Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66726d51aa15979075f2478fad04f7f0a2ed2591d65635cbf69cff5b1a8667ce

Tx prefix hash: 4ee8fdc693fb7a1b3ef4e4df4d9cc5a5c79562001cf02fec48da3dca46e6a328
Tx public key: 2185ea00eda162ae509bdf575d3c92efa154537af2614cf10cc914bd6f2643d1
Timestamp: 1742991010 Timestamp [UCT]: 2025-03-26 12:10:10 Age [y:d:h:m:s]: 00:288:07:32:56
Block: 1247665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203887 RingCT/type: yes/0
Extra: 012185ea00eda162ae509bdf575d3c92efa154537af2614cf10cc914bd6f2643d102110000000ed2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3990e3d2b3a16fd8313f47addbc2a2e260101db9872118070a4f4da83de68d1 0.600000000000 1734692 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": 1247675, "vin": [ { "gen": { "height": 1247665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3990e3d2b3a16fd8313f47addbc2a2e260101db9872118070a4f4da83de68d1" } } ], "extra": [ 1, 33, 133, 234, 0, 237, 161, 98, 174, 80, 155, 223, 87, 93, 60, 146, 239, 161, 84, 83, 122, 242, 97, 76, 241, 12, 201, 20, 189, 111, 38, 67, 209, 2, 17, 0, 0, 0, 14, 210, 228, 14, 253, 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