Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1218f907b767649137b175c56c448065c2ea2695234bc663fc4b9b19b15077c6

Tx prefix hash: 00c9092bb62d8d98bb6262452f1839e60d9cbd9aca643484db0d9dce8ad418cb
Tx public key: 027bc57cb2576c43b3a2ff92d8f0dc9539610a1a57ab371d5974323aed90c77c
Timestamp: 1728523366 Timestamp [UCT]: 2024-10-10 01:22:46 Age [y:d:h:m:s]: 00:161:17:56:13
Block: 1128215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115404 RingCT/type: yes/0
Extra: 01027bc57cb2576c43b3a2ff92d8f0dc9539610a1a57ab371d5974323aed90c77c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 771559e4c541ef5d5f6ddeee019378d949896fa522058a926c1404c266aebc1a 0.600000000000 1611032 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": 1128225, "vin": [ { "gen": { "height": 1128215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "771559e4c541ef5d5f6ddeee019378d949896fa522058a926c1404c266aebc1a" } } ], "extra": [ 1, 2, 123, 197, 124, 178, 87, 108, 67, 179, 162, 255, 146, 216, 240, 220, 149, 57, 97, 10, 26, 87, 171, 55, 29, 89, 116, 50, 58, 237, 144, 199, 124, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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