Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f60956748ff39a33a07dfa01b23dfea875b69e09ec4d615d5371d5b9cf2ab4

Tx prefix hash: c8c7fad567b4b665f937a75dbe12b0edd21a949421b26c3a5d7035f7f4c46903
Tx public key: 1fae14f192d36eefc97b15a669f66fdc02b983c3afe212c1e8a66c981c650957
Timestamp: 1761301630 Timestamp [UCT]: 2025-10-24 10:27:10 Age [y:d:h:m:s]: 00:015:17:25:57
Block: 1396859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11249 RingCT/type: yes/0
Extra: 011fae14f192d36eefc97b15a669f66fdc02b983c3afe212c1e8a66c981c6509570211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1bf9f0dff4c50180e496d50ee176e4784143030c20928bd8cd1965c899e4bb4 0.600000000000 1885146 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": 1396869, "vin": [ { "gen": { "height": 1396859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1bf9f0dff4c50180e496d50ee176e4784143030c20928bd8cd1965c899e4bb4" } } ], "extra": [ 1, 31, 174, 20, 241, 146, 211, 110, 239, 201, 123, 21, 166, 105, 246, 111, 220, 2, 185, 131, 195, 175, 226, 18, 193, 232, 166, 108, 152, 28, 101, 9, 87, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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