Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 012f225f32cdd0f34bec9a0d3171766c9c9cc4021ed529dd70defe217b87528f

Tx prefix hash: 6660c53fd8c7a7ce78db9c2bd1964e34c7da17741f1cfa62964e44913f258bb4
Tx public key: 2871bb6407373c8302a838a4e8a5a4d25f55496ef3cf8b0ec64452898ca934e9
Timestamp: 1714995137 Timestamp [UCT]: 2024-05-06 11:32:17 Age [y:d:h:m:s]: 00:339:09:40:40
Block: 1016060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242611 RingCT/type: yes/0
Extra: 012871bb6407373c8302a838a4e8a5a4d25f55496ef3cf8b0ec64452898ca934e90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a248f8aeb51ec272724fe7d76b2de9e1d51c598d5a0f42769c3921f5e8724c21 0.600000000000 1479539 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": 1016070, "vin": [ { "gen": { "height": 1016060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a248f8aeb51ec272724fe7d76b2de9e1d51c598d5a0f42769c3921f5e8724c21" } } ], "extra": [ 1, 40, 113, 187, 100, 7, 55, 60, 131, 2, 168, 56, 164, 232, 165, 164, 210, 95, 85, 73, 110, 243, 207, 139, 14, 198, 68, 82, 137, 140, 169, 52, 233, 2, 17, 0, 0, 0, 1, 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