Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5242f1a710397b31837413e221e2a17c383a09097605fe810b9af112277bf3e7

Tx prefix hash: 9964898e9c6a5f10d1855dd3e44c7248311636b4c86d93cb03d812ce9b7d9cb4
Tx public key: 005452a7b642c86f9a3dc0c0054146bbdb5822b325a7623f7050d3ce3b2075fd
Timestamp: 1709315828 Timestamp [UCT]: 2024-03-01 17:57:08 Age [y:d:h:m:s]: 01:040:06:21:46
Block: 968993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289773 RingCT/type: yes/0
Extra: 01005452a7b642c86f9a3dc0c0054146bbdb5822b325a7623f7050d3ce3b2075fd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df00c51490a655303bf8800dfa017bee60994ee33d259a6e4921238cd7b63f0e 0.600000000000 1428820 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": 969003, "vin": [ { "gen": { "height": 968993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df00c51490a655303bf8800dfa017bee60994ee33d259a6e4921238cd7b63f0e" } } ], "extra": [ 1, 0, 84, 82, 167, 182, 66, 200, 111, 154, 61, 192, 192, 5, 65, 70, 187, 219, 88, 34, 179, 37, 167, 98, 63, 112, 80, 211, 206, 59, 32, 117, 253, 2, 17, 0, 0, 0, 1, 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