Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a783bdb3a227aac151b185fa5503ff96d3d5da001652c1e1f47132a0d7c1e8bb

Tx prefix hash: 20dc1e62ce9771449f9385e52d7e7bb151b1ae6c9c541ae3ba302a9b54fad2fe
Tx public key: 6dd878a55445e1a0217d886faef0c3d78d3e49607af43620af9c94a8491728d4
Timestamp: 1649249528 Timestamp [UCT]: 2022-04-06 12:52:08 Age [y:d:h:m:s]: 02:265:20:32:50
Block: 474439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709758 RingCT/type: yes/0
Extra: 016dd878a55445e1a0217d886faef0c3d78d3e49607af43620af9c94a8491728d40211000000054a0f5013000000000000000000

1 output(s) for total of 16.443220740000 dcy

stealth address amount amount idx
00: c583e6ae34abf957193f2dffc1364f1bdc0a193ef0af57920ad522ca39759a02 16.443220740000 894476 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": 474449, "vin": [ { "gen": { "height": 474439 } } ], "vout": [ { "amount": 16443220740, "target": { "key": "c583e6ae34abf957193f2dffc1364f1bdc0a193ef0af57920ad522ca39759a02" } } ], "extra": [ 1, 109, 216, 120, 165, 84, 69, 225, 160, 33, 125, 136, 111, 174, 240, 195, 215, 141, 62, 73, 96, 122, 244, 54, 32, 175, 156, 148, 168, 73, 23, 40, 212, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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