Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51a9fc7acd6660d04d796858aba5b711c5caa524821585d77a299af5d1670d3

Tx prefix hash: dc614e0854002e8fc8ebfdaebcef59d02eeaf2aa809a51e9d07bbe0ff8459a33
Tx public key: 7f9ba5aebd03e002064fcb485e96ae33f357c855a1804564c264a2a844f734de
Timestamp: 1751983980 Timestamp [UCT]: 2025-07-08 14:13:00 Age [y:d:h:m:s]: 00:207:20:35:09
Block: 1321362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146912 RingCT/type: yes/0
Extra: 017f9ba5aebd03e002064fcb485e96ae33f357c855a1804564c264a2a844f734de021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b8e1ef13efc70f3e473a49ef60eba5c3bbbcae86f6670e4a551eb23c01ed64 0.600000000000 1809067 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": 1321372, "vin": [ { "gen": { "height": 1321362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b8e1ef13efc70f3e473a49ef60eba5c3bbbcae86f6670e4a551eb23c01ed64" } } ], "extra": [ 1, 127, 155, 165, 174, 189, 3, 224, 2, 6, 79, 203, 72, 94, 150, 174, 51, 243, 87, 200, 85, 161, 128, 69, 100, 194, 100, 162, 168, 68, 247, 52, 222, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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