Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0292f611cdfdba559fb10288da000ca4621727e12a7f41c03d3f135b15d2465e

Tx prefix hash: c5df48f191dbc12a28069dba66675f4a162b7c54fd77e20039d6554ecd6c307b
Tx public key: c1fcd86ebc192415449c57dc2fc1bc63373810f7ce06858944f6bfdf310cd3e0
Timestamp: 1702724556 Timestamp [UCT]: 2023-12-16 11:02:36 Age [y:d:h:m:s]: 01:329:06:13:17
Block: 914332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494177 RingCT/type: yes/0
Extra: 01c1fcd86ebc192415449c57dc2fc1bc63373810f7ce06858944f6bfdf310cd3e002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4e6fbe565f97b7fd5a6c8d8fd17a70edf48ebd942b5b6d9731d90812b2a34b 0.600000000000 1371646 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 914342, "vin": [ { "gen": { "height": 914332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4e6fbe565f97b7fd5a6c8d8fd17a70edf48ebd942b5b6d9731d90812b2a34b" } } ], "extra": [ 1, 193, 252, 216, 110, 188, 25, 36, 21, 68, 156, 87, 220, 47, 193, 188, 99, 55, 56, 16, 247, 206, 6, 133, 137, 68, 246, 191, 223, 49, 12, 211, 224, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8