Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab439625d7c876d70ba20e1d4b865d914ad937d03606b22fa1d55b636059d30f

Tx prefix hash: 6ef3e0b4abd4077bf9a7431958746aa1f17de8a526702e70692bd5f8c3a0fdf3
Tx public key: ff1bede0f863c0d02fe5f1f64c65fb273c4da04f570cc3852db7198938084659
Timestamp: 1746066842 Timestamp [UCT]: 2025-05-01 02:34:02 Age [y:d:h:m:s]: 00:195:08:36:44
Block: 1273131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137342 RingCT/type: yes/0
Extra: 01ff1bede0f863c0d02fe5f1f64c65fb273c4da04f570cc3852db7198938084659021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00125a1c81e5b7317e55570664c460478b2c492cd3f9dbc086a1858cec7d6d5d 0.600000000000 1760412 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": 1273141, "vin": [ { "gen": { "height": 1273131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00125a1c81e5b7317e55570664c460478b2c492cd3f9dbc086a1858cec7d6d5d" } } ], "extra": [ 1, 255, 27, 237, 224, 248, 99, 192, 208, 47, 229, 241, 246, 76, 101, 251, 39, 60, 77, 160, 79, 87, 12, 195, 133, 45, 183, 25, 137, 56, 8, 70, 89, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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