Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee63132739a3f9867c7a7c4dffd641893271bb980afc0c930856680d9f854e71

Tx prefix hash: e42b6641eb82467876aac5a102ed38298f072751609d7a72e7312f0c46ddc5e4
Tx public key: f57169b458fef6256e87d3e32cfcf6f5d1390d6d99706cff6e7a8f942b6982dd
Timestamp: 1720331101 Timestamp [UCT]: 2024-07-07 05:45:01 Age [y:d:h:m:s]: 00:326:14:47:30
Block: 1060301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233417 RingCT/type: yes/0
Extra: 01f57169b458fef6256e87d3e32cfcf6f5d1390d6d99706cff6e7a8f942b6982dd02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8309abd43b3746fc99fb69da9af4c60ba67ab000db311ae6110945c5ac4f35e2 0.600000000000 1530772 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": 1060311, "vin": [ { "gen": { "height": 1060301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8309abd43b3746fc99fb69da9af4c60ba67ab000db311ae6110945c5ac4f35e2" } } ], "extra": [ 1, 245, 113, 105, 180, 88, 254, 246, 37, 110, 135, 211, 227, 44, 252, 246, 245, 209, 57, 13, 109, 153, 112, 108, 255, 110, 122, 143, 148, 43, 105, 130, 221, 2, 17, 0, 0, 0, 11, 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