Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65e71d67e89e99a89ebe0a53c0de2b77a1b99c1808d8abd548e5c93259b056f

Tx prefix hash: 0b0519d544ad2e32ccec7e4cc14782d96b7d2a2f46d8015994b798452aa64085
Tx public key: fc800f134e0dc4719a8cadf9f14ec4fb19b406077acb9c65f6d3a896129847d2
Timestamp: 1700699855 Timestamp [UCT]: 2023-11-23 00:37:35 Age [y:d:h:m:s]: 01:101:22:08:09
Block: 897541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334001 RingCT/type: yes/0
Extra: 01fc800f134e0dc4719a8cadf9f14ec4fb19b406077acb9c65f6d3a896129847d202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.651739536000 dcy

stealth address amount amount idx
00: b89d64e3a83fa7c1bb71c1ea9d2434a2089e094b610be01110bd035c873f64f1 0.651739536000 1353922 of 0

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": 897551, "vin": [ { "gen": { "height": 897541 } } ], "vout": [ { "amount": 651739536, "target": { "key": "b89d64e3a83fa7c1bb71c1ea9d2434a2089e094b610be01110bd035c873f64f1" } } ], "extra": [ 1, 252, 128, 15, 19, 78, 13, 196, 113, 154, 140, 173, 249, 241, 78, 196, 251, 25, 180, 6, 7, 122, 203, 156, 101, 246, 211, 168, 150, 18, 152, 71, 210, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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