Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5471b0af1bebd91ed29ad229e13e408ffa9af164b008ef3d00e87e11aad47a

Tx prefix hash: f9a43d6b5b35f884618e74e91860fb4ef81fdd0193c49750d44ec6cbc9a1bb75
Tx public key: 17ce62ea4ee94d42969ca9d38c216e836aeb8fcd837d7575b2b06a5d95ec4d74
Timestamp: 1681638244 Timestamp [UCT]: 2023-04-16 09:44:04 Age [y:d:h:m:s]: 01:362:04:11:07
Block: 739765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520122 RingCT/type: yes/0
Extra: 0117ce62ea4ee94d42969ca9d38c216e836aeb8fcd837d7575b2b06a5d95ec4d74021100000001b3164c24000000000000000000

1 output(s) for total of 2.171959296000 dcy

stealth address amount amount idx
00: 7a8dcc0958d7f3d93d871dc1fdda9146618756ebc7eb513df51e0ec2560d6c61 2.171959296000 1186638 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": 739775, "vin": [ { "gen": { "height": 739765 } } ], "vout": [ { "amount": 2171959296, "target": { "key": "7a8dcc0958d7f3d93d871dc1fdda9146618756ebc7eb513df51e0ec2560d6c61" } } ], "extra": [ 1, 23, 206, 98, 234, 78, 233, 77, 66, 150, 156, 169, 211, 140, 33, 110, 131, 106, 235, 143, 205, 131, 125, 117, 117, 178, 176, 106, 93, 149, 236, 77, 116, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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