Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e64d7e6abdcdf7ae07bf1c49abfc9777c1e87704dc3f2205f297ac279784b15

Tx prefix hash: a0de8b4d9ea8117a573239409d380d7e1037acbf062f4b1da7e160acafe15b5a
Tx public key: 9f1968d8ada9598afc41d61b69b76130f0dd039445d77a6fbe631d3ca4dc18e8
Timestamp: 1741867054 Timestamp [UCT]: 2025-03-13 11:57:34 Age [y:d:h:m:s]: 00:251:15:36:03
Block: 1238393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177582 RingCT/type: yes/0
Extra: 019f1968d8ada9598afc41d61b69b76130f0dd039445d77a6fbe631d3ca4dc18e80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e937703c4e23627ccc1203ef1928419b644cbe936d718bb4e442b439c4858811 0.600000000000 1725352 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": 1238403, "vin": [ { "gen": { "height": 1238393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e937703c4e23627ccc1203ef1928419b644cbe936d718bb4e442b439c4858811" } } ], "extra": [ 1, 159, 25, 104, 216, 173, 169, 89, 138, 252, 65, 214, 27, 105, 183, 97, 48, 240, 221, 3, 148, 69, 215, 122, 111, 190, 99, 29, 60, 164, 220, 24, 232, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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