Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10bfa4aa4a83bbf177eb70417df38611c7dce4a64e2bbbf459f77246a0ea9a54

Tx prefix hash: 2f9ab4c6010d20f50ba6f1041c38ae4121a94adc6260d82bf79ad92cefd806d3
Tx public key: 39217d0ae1a3dfa8bffd0bf72a04e36369dc2be5dc6664efb0b2141f28f6f988
Timestamp: 1577553489 Timestamp [UCT]: 2019-12-28 17:18:09 Age [y:d:h:m:s]: 05:067:02:51:04
Block: 33643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197820 RingCT/type: yes/0
Extra: 0139217d0ae1a3dfa8bffd0bf72a04e36369dc2be5dc6664efb0b2141f28f6f98802110000000a8a2ee0d9000000000000000000

1 output(s) for total of 474.818500403000 dcy

stealth address amount amount idx
00: 378fdd975a716d9a3539186a4b0deab10db821000507744988595733eb704814 474.818500403000 56415 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": 33653, "vin": [ { "gen": { "height": 33643 } } ], "vout": [ { "amount": 474818500403, "target": { "key": "378fdd975a716d9a3539186a4b0deab10db821000507744988595733eb704814" } } ], "extra": [ 1, 57, 33, 125, 10, 225, 163, 223, 168, 191, 253, 11, 247, 42, 4, 227, 99, 105, 220, 43, 229, 220, 102, 100, 239, 176, 178, 20, 31, 40, 246, 249, 136, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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