Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15ce6c2c79f844602a67767b7804a0666daa7bb1d74319d9f42e1c340b7fc827

Tx prefix hash: f1d6b2a0d39a7646d494f4227a31f16581b43e678b2910282b96dcc92ac22f1f
Tx public key: ed46c8b11ae947e5aadedb693f4767d44f9dc2d62be28ce5033c8713655963f9
Timestamp: 1726463444 Timestamp [UCT]: 2024-09-16 05:10:44 Age [y:d:h:m:s]: 00:188:04:15:57
Block: 1111136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134320 RingCT/type: yes/0
Extra: 01ed46c8b11ae947e5aadedb693f4767d44f9dc2d62be28ce5033c8713655963f9021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed20cfff79627175a09cf3a9b1bd981df2b5af23333e66c766a50d921b176526 0.600000000000 1589991 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": 1111146, "vin": [ { "gen": { "height": 1111136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed20cfff79627175a09cf3a9b1bd981df2b5af23333e66c766a50d921b176526" } } ], "extra": [ 1, 237, 70, 200, 177, 26, 233, 71, 229, 170, 222, 219, 105, 63, 71, 103, 212, 79, 157, 194, 214, 43, 226, 140, 229, 3, 60, 135, 19, 101, 89, 99, 249, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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