Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e444073a54543e79be74b05814066b72cf6c783502accc31c49290aa55281f3d

Tx prefix hash: d9686a45a66063ef080fb985742f5bb62fcd41b54d74aeb89ab90edf42fe8b30
Tx public key: 8f1ca6df49011baa1259b62058a51afe3e5af8fdefb1b96e531b9c30ff5584d2
Timestamp: 1684880828 Timestamp [UCT]: 2023-05-23 22:27:08 Age [y:d:h:m:s]: 01:349:17:04:50
Block: 766647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511183 RingCT/type: yes/0
Extra: 018f1ca6df49011baa1259b62058a51afe3e5af8fdefb1b96e531b9c30ff5584d2021100000006faf35c9c000000000000000000

1 output(s) for total of 1.769214204000 dcy

stealth address amount amount idx
00: ef0d6ed0d5dded7b479877644264e0cad66110dc4bd3346cb25a599ae75415b8 1.769214204000 1215702 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": 766657, "vin": [ { "gen": { "height": 766647 } } ], "vout": [ { "amount": 1769214204, "target": { "key": "ef0d6ed0d5dded7b479877644264e0cad66110dc4bd3346cb25a599ae75415b8" } } ], "extra": [ 1, 143, 28, 166, 223, 73, 1, 27, 170, 18, 89, 182, 32, 88, 165, 26, 254, 62, 90, 248, 253, 239, 177, 185, 110, 83, 27, 156, 48, 255, 85, 132, 210, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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