Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd4a8f7a35dd24aba1ab96a405318997d78793954d66321143549187789bea6b

Tx prefix hash: d0c624d68c7b3680e181e1590b05dda3536098f8e5b1d23745a22ad5e7114a0e
Tx public key: 9361de11b76ba838de09156cdea3e8dec3f664dd7d5d9cb8d875dfddf715f8dc
Timestamp: 1766185614 Timestamp [UCT]: 2025-12-19 23:06:54 Age [y:d:h:m:s]: 00:001:18:23:15
Block: 1437326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1262 RingCT/type: yes/0
Extra: 019361de11b76ba838de09156cdea3e8dec3f664dd7d5d9cb8d875dfddf715f8dc0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b827e295016eab3dca4f0f874e8c362d777b4f6513d93dae13ba15756fb853 0.600000000000 1926133 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": 1437336, "vin": [ { "gen": { "height": 1437326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b827e295016eab3dca4f0f874e8c362d777b4f6513d93dae13ba15756fb853" } } ], "extra": [ 1, 147, 97, 222, 17, 183, 107, 168, 56, 222, 9, 21, 108, 222, 163, 232, 222, 195, 246, 100, 221, 125, 93, 156, 184, 216, 117, 223, 221, 247, 21, 248, 220, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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