Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fd07493123d23964bab1537559f48b38115b1bdb58d5710238c93462a5aa84a

Tx prefix hash: 0213a98b2677cd3f7622f4542013010f4c9772ec69db3f1d27f30b1463ead910
Tx public key: 87b03351b8b3f41a2b7676c3fbf541117dd8ab473c26925607d34765b4d10d3d
Timestamp: 1737928301 Timestamp [UCT]: 2025-01-26 21:51:41 Age [y:d:h:m:s]: 00:142:12:49:13
Block: 1205909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101683 RingCT/type: yes/0
Extra: 0187b03351b8b3f41a2b7676c3fbf541117dd8ab473c26925607d34765b4d10d3d02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e576f60a8e766536315f7dd3704c45f7dfd81807fcb44d98df0504827a3d9f0 0.600000000000 1692608 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": 1205919, "vin": [ { "gen": { "height": 1205909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e576f60a8e766536315f7dd3704c45f7dfd81807fcb44d98df0504827a3d9f0" } } ], "extra": [ 1, 135, 176, 51, 81, 184, 179, 244, 26, 43, 118, 118, 195, 251, 245, 65, 17, 125, 216, 171, 71, 60, 38, 146, 86, 7, 211, 71, 101, 180, 209, 13, 61, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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