Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f3a80911eb9c17310efef8cf71bf7894c1d441193d8018e3cdb7d027a4d75e

Tx prefix hash: 27866962feec90637331c53cc9fe1d915edade8694b182b55fba451b76357519
Tx public key: ab691c40fb54bf475576c60b6c83d3f9c4123f0d137a152b536809aded234c20
Timestamp: 1705110044 Timestamp [UCT]: 2024-01-13 01:40:44 Age [y:d:h:m:s]: 01:067:00:36:04
Block: 934088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309026 RingCT/type: yes/0
Extra: 01ab691c40fb54bf475576c60b6c83d3f9c4123f0d137a152b536809aded234c200211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 778b68ed7c9403e69a9c9bc95d669a90cb15bce2b36b6aadb8e924eefd379fd3 0.600000000000 1392074 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": 934098, "vin": [ { "gen": { "height": 934088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "778b68ed7c9403e69a9c9bc95d669a90cb15bce2b36b6aadb8e924eefd379fd3" } } ], "extra": [ 1, 171, 105, 28, 64, 251, 84, 191, 71, 85, 118, 198, 11, 108, 131, 211, 249, 196, 18, 63, 13, 19, 122, 21, 43, 83, 104, 9, 173, 237, 35, 76, 32, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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