Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc5fd577a8313dedf00863f734125e131445ec0b9303d1dc180ecab81b16c6a

Tx prefix hash: de0cd696a14f01113936477db3ff1caf2fb95c4dc51f652a85b4634c616d6bcf
Tx public key: f64dad353b1f7e12220b85cd5d849c01e08fdefd27d69cda1aa2f20c32934e69
Timestamp: 1709443526 Timestamp [UCT]: 2024-03-03 05:25:26 Age [y:d:h:m:s]: 01:107:02:05:25
Block: 970042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337457 RingCT/type: yes/0
Extra: 01f64dad353b1f7e12220b85cd5d849c01e08fdefd27d69cda1aa2f20c32934e6902110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a6471d2ef7dfdc522e114c9de266543547770b8d5536afd7055501b1069b24 0.600000000000 1429891 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": 970052, "vin": [ { "gen": { "height": 970042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a6471d2ef7dfdc522e114c9de266543547770b8d5536afd7055501b1069b24" } } ], "extra": [ 1, 246, 77, 173, 53, 59, 31, 126, 18, 34, 11, 133, 205, 93, 132, 156, 1, 224, 143, 222, 253, 39, 214, 156, 218, 26, 162, 242, 12, 50, 147, 78, 105, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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