Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a66ac23adf428fa256b18c4c2569ad67b9527cb755e019dd0479cc98e68a8ad

Tx prefix hash: dc3d52a10bcd565de7c3e0220194b084383c4c19d506fe8f803e0cd10a9a41ce
Tx public key: f88162dee3bc0cb83a790ca513d69aecb95851cfb89d066cc2a54433601fa92d
Timestamp: 1717378232 Timestamp [UCT]: 2024-06-03 01:30:32 Age [y:d:h:m:s]: 00:346:23:57:58
Block: 1035825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248003 RingCT/type: yes/0
Extra: 01f88162dee3bc0cb83a790ca513d69aecb95851cfb89d066cc2a54433601fa92d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c82ecaee4a6326d98373e7dee846d218f7843545355e3d4661a428f8e469f827 0.600000000000 1504348 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": 1035835, "vin": [ { "gen": { "height": 1035825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c82ecaee4a6326d98373e7dee846d218f7843545355e3d4661a428f8e469f827" } } ], "extra": [ 1, 248, 129, 98, 222, 227, 188, 12, 184, 58, 121, 12, 165, 19, 214, 154, 236, 185, 88, 81, 207, 184, 157, 6, 108, 194, 165, 68, 51, 96, 31, 169, 45, 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