Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e59fe76a30b8987e6155ffd3e99d953a81b9217251bf67ba88d071960e2be5b1

Tx prefix hash: dc080eb6e3a166be003db24d683e810343a204be487a8a5b73753b2d03d1038f
Tx public key: 511a2c0dd64b9eb9bc2ec87b6df5d082b23d326377a7abec877280ff94fcd1d1
Timestamp: 1702671929 Timestamp [UCT]: 2023-12-15 20:25:29 Age [y:d:h:m:s]: 01:330:11:12:10
Block: 913895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495042 RingCT/type: yes/0
Extra: 01511a2c0dd64b9eb9bc2ec87b6df5d082b23d326377a7abec877280ff94fcd1d102110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdbeeb49fc8afc564c91d17ae540087b960f462ecbcec9d9fe84e1165bd41f39 0.600000000000 1371175 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": 913905, "vin": [ { "gen": { "height": 913895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdbeeb49fc8afc564c91d17ae540087b960f462ecbcec9d9fe84e1165bd41f39" } } ], "extra": [ 1, 81, 26, 44, 13, 214, 75, 158, 185, 188, 46, 200, 123, 109, 245, 208, 130, 178, 61, 50, 99, 119, 167, 171, 236, 135, 114, 128, 255, 148, 252, 209, 209, 2, 17, 0, 0, 0, 10, 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