Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5351220fe3ab4a95932fd9b4f56b1692721015fe4503eca55447014e0e033baf

Tx prefix hash: 815aaa9d23a785150d59c38be1196cc57a770639aec13cd704badf9fe9b9d9f6
Tx public key: 0723a0a114b1fcf311e820b7a72847b29ff5d5be3903dd93bc763aeb6699b523
Timestamp: 1736632895 Timestamp [UCT]: 2025-01-11 22:01:35 Age [y:d:h:m:s]: 00:066:22:45:21
Block: 1195304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47649 RingCT/type: yes/0
Extra: 010723a0a114b1fcf311e820b7a72847b29ff5d5be3903dd93bc763aeb6699b5230211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 618f60170bf8b4b63b013a40996e2aa43eab1200e50d726193fb2d8cb4fc191c 0.600000000000 1681893 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": 1195314, "vin": [ { "gen": { "height": 1195304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "618f60170bf8b4b63b013a40996e2aa43eab1200e50d726193fb2d8cb4fc191c" } } ], "extra": [ 1, 7, 35, 160, 161, 20, 177, 252, 243, 17, 232, 32, 183, 167, 40, 71, 178, 159, 245, 213, 190, 57, 3, 221, 147, 188, 118, 58, 235, 102, 153, 181, 35, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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