Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea8f43d83d86d282e63e987c8f98c02385624cba12f2601502951566c36bf75

Tx prefix hash: 70ae7dc6e22453a1d54be9e4c9838f32d6f491c02b1edbdb606b5c649e9642b4
Tx public key: fa313a280987cbfc1ff8de4ac340edd482e27e6b2e1af427cb1cecdd603499f0
Timestamp: 1760742476 Timestamp [UCT]: 2025-10-17 23:07:56 Age [y:d:h:m:s]: 00:066:20:39:51
Block: 1392228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47846 RingCT/type: yes/0
Extra: 01fa313a280987cbfc1ff8de4ac340edd482e27e6b2e1af427cb1cecdd603499f00211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 292759179b48130a1d6fa1246f5ae9f084a2154fca3de8d8851896c11e151c60 0.600000000000 1880479 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": 1392238, "vin": [ { "gen": { "height": 1392228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "292759179b48130a1d6fa1246f5ae9f084a2154fca3de8d8851896c11e151c60" } } ], "extra": [ 1, 250, 49, 58, 40, 9, 135, 203, 252, 31, 248, 222, 74, 195, 64, 237, 212, 130, 226, 126, 107, 46, 26, 244, 39, 203, 28, 236, 221, 96, 52, 153, 240, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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