Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6404c971ac3fd7e305294850bd16c681c0d04022c1666c8a162a73aca3225d

Tx prefix hash: 4372c344efa065d9f5c785e383703df0f89271bf5ca60e3f4b44bf3844013b3d
Tx public key: 1d901d14e0e8efb1449fa6f7df06f0980734a10206ca090afc6e7cab8b0b8d2d
Timestamp: 1583640139 Timestamp [UCT]: 2020-03-08 04:02:19 Age [y:d:h:m:s]: 05:032:16:06:41
Block: 78562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178644 RingCT/type: yes/0
Extra: 011d901d14e0e8efb1449fa6f7df06f0980734a10206ca090afc6e7cab8b0b8d2d0211000000135143fba2000000000000000000

1 output(s) for total of 337.048402773000 dcy

stealth address amount amount idx
00: 87d003fc5139d2b65531404f32e3c82a4a46a372875d06a93adf341567e22763 337.048402773000 144028 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": 78572, "vin": [ { "gen": { "height": 78562 } } ], "vout": [ { "amount": 337048402773, "target": { "key": "87d003fc5139d2b65531404f32e3c82a4a46a372875d06a93adf341567e22763" } } ], "extra": [ 1, 29, 144, 29, 20, 224, 232, 239, 177, 68, 159, 166, 247, 223, 6, 240, 152, 7, 52, 161, 2, 6, 202, 9, 10, 252, 110, 124, 171, 139, 11, 141, 45, 2, 17, 0, 0, 0, 19, 81, 67, 251, 162, 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