Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 580ac704a18f19eeae30539d947398adc07880f8f2df607d8931a81cf853601e

Tx prefix hash: 0eefbe4b08dcd849eda346a50c3cbc48c2f3a16b1ba9488212977c56f0c236dd
Tx public key: e9c4e896d6a5ec35f04732c24cda72263b5956286250ac83c772174ba01f3a90
Timestamp: 1715540344 Timestamp [UCT]: 2024-05-12 18:59:04 Age [y:d:h:m:s]: 01:016:17:28:59
Block: 1020611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272876 RingCT/type: yes/0
Extra: 01e9c4e896d6a5ec35f04732c24cda72263b5956286250ac83c772174ba01f3a9002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 155ff18e29ed2b9dc2ad52437c1a041edc526f24b37bf8f006c54e3d5b593937 0.600000000000 1484692 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": 1020621, "vin": [ { "gen": { "height": 1020611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "155ff18e29ed2b9dc2ad52437c1a041edc526f24b37bf8f006c54e3d5b593937" } } ], "extra": [ 1, 233, 196, 232, 150, 214, 165, 236, 53, 240, 71, 50, 194, 76, 218, 114, 38, 59, 89, 86, 40, 98, 80, 172, 131, 199, 114, 23, 75, 160, 31, 58, 144, 2, 17, 0, 0, 0, 3, 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