Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 845b0086adba3b9c17f43f7b705fe5bec8d8b2f63d7ccccc407ebbcca8082569

Tx prefix hash: 866f1c615635e358f1d1d2a54222b94e14af2840fc63dc6c79fe0d940a2fea69
Tx public key: c785a356d653af09b109ebf6d9d38f4c11ff3d5ccc1938d3c6e9c39fc542e514
Timestamp: 1574983047 Timestamp [UCT]: 2019-11-28 23:17:27 Age [y:d:h:m:s]: 05:166:12:54:07
Block: 19284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1262015 RingCT/type: yes/0
Extra: 01c785a356d653af09b109ebf6d9d38f4c11ff3d5ccc1938d3c6e9c39fc542e51402110000001fa47741aa000000000000000000

1 output(s) for total of 529.791493332000 dcy

stealth address amount amount idx
00: 347fec09b8bd3ef1a61ddfcf285308713c11cdd2ffc791c054bad59e9686b344 529.791493332000 30301 of 0

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": 19294, "vin": [ { "gen": { "height": 19284 } } ], "vout": [ { "amount": 529791493332, "target": { "key": "347fec09b8bd3ef1a61ddfcf285308713c11cdd2ffc791c054bad59e9686b344" } } ], "extra": [ 1, 199, 133, 163, 86, 214, 83, 175, 9, 177, 9, 235, 246, 217, 211, 143, 76, 17, 255, 61, 92, 204, 25, 56, 211, 198, 233, 195, 159, 197, 66, 229, 20, 2, 17, 0, 0, 0, 31, 164, 119, 65, 170, 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