Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d0e5c12a4eedc8e9876be3f2c5e4b0ceafa3fa5ddf48bb4c12cbe5194a2d45

Tx prefix hash: d0c0101ac52490438d49b6ff80f34e2cd15adda2a74719b13d0574a3b07cdfc4
Tx public key: 87bf8fbc77f9575a15d96e8b0cd3f88e721121eac8a2ed74c712218e6f574243
Timestamp: 1713856190 Timestamp [UCT]: 2024-04-23 07:09:50 Age [y:d:h:m:s]: 00:205:01:18:40
Block: 1006623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146783 RingCT/type: yes/0
Extra: 0187bf8fbc77f9575a15d96e8b0cd3f88e721121eac8a2ed74c712218e6f5742430211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4d072b8a70b8d4680a9cab3512b9fa324f8aec86c3f9084d4c3d85ca5e4c90 0.600000000000 1467705 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": 1006633, "vin": [ { "gen": { "height": 1006623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4d072b8a70b8d4680a9cab3512b9fa324f8aec86c3f9084d4c3d85ca5e4c90" } } ], "extra": [ 1, 135, 191, 143, 188, 119, 249, 87, 90, 21, 217, 110, 139, 12, 211, 248, 142, 114, 17, 33, 234, 200, 162, 237, 116, 199, 18, 33, 142, 111, 87, 66, 67, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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