Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b02de672213592db6406ee1773f0696abbc4bda523f2b4b2da4fbe3f28dd46

Tx prefix hash: a0e467fc651163bb3e04621c387fb7178164479ae021e4703b36e9246d48c8a8
Tx public key: 8cd6bdfd72208e0af7df25d2a0019c848d627e3d87e4e4d14cf7fb23e2a9a015
Timestamp: 1706697468 Timestamp [UCT]: 2024-01-31 10:37:48 Age [y:d:h:m:s]: 01:092:23:49:39
Block: 947252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327556 RingCT/type: yes/0
Extra: 018cd6bdfd72208e0af7df25d2a0019c848d627e3d87e4e4d14cf7fb23e2a9a01502110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4d47065a9bf9ec73ce8ba0252a97b2ff0169f5b2df06109091eb5bc62911c28 0.600000000000 1405600 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": 947262, "vin": [ { "gen": { "height": 947252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4d47065a9bf9ec73ce8ba0252a97b2ff0169f5b2df06109091eb5bc62911c28" } } ], "extra": [ 1, 140, 214, 189, 253, 114, 32, 142, 10, 247, 223, 37, 210, 160, 1, 156, 132, 141, 98, 126, 61, 135, 228, 228, 209, 76, 247, 251, 35, 226, 169, 160, 21, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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