Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d06b98f4f64b07f8dafece27a5290b0477f8b64a43052f73be916bd209d64f

Tx prefix hash: 1e7d733c6f951f95caa9b2af0162271041de22a5e267842fc010c7a4a4186272
Tx public key: a5e9c567e5afcf5906a3148d8dcb7f952aded7a8bd59e6b739478d458e7e6c34
Timestamp: 1696702463 Timestamp [UCT]: 2023-10-07 18:14:23 Age [y:d:h:m:s]: 01:101:22:39:55
Block: 864609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334122 RingCT/type: yes/0
Extra: 01a5e9c567e5afcf5906a3148d8dcb7f952aded7a8bd59e6b739478d458e7e6c34021100000005faf35c9c000000000000000000

1 output(s) for total of 0.837898672000 dcy

stealth address amount amount idx
00: edddfe22e73d025a2f20072f4278dc95497a70c65f67d036042011bd9b2e07a8 0.837898672000 1319129 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": 864619, "vin": [ { "gen": { "height": 864609 } } ], "vout": [ { "amount": 837898672, "target": { "key": "edddfe22e73d025a2f20072f4278dc95497a70c65f67d036042011bd9b2e07a8" } } ], "extra": [ 1, 165, 233, 197, 103, 229, 175, 207, 89, 6, 163, 20, 141, 141, 203, 127, 149, 42, 222, 215, 168, 189, 89, 230, 183, 57, 71, 141, 69, 142, 126, 108, 52, 2, 17, 0, 0, 0, 5, 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