Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6126d72cb261fa7fd5756ffd283bb60fd702f01b830791bc78a8aadf515bb8e

Tx prefix hash: c89a9442e28aeeb5a857704b9b03d4dbb73ba578b2677b77d74f5d8db4da66fd
Tx public key: 3ec6aa0ec614bac53874cfe8345bdfb52e4f49c95e75f9324b489b393864ba25
Timestamp: 1728385475 Timestamp [UCT]: 2024-10-08 11:04:35 Age [y:d:h:m:s]: 01:034:20:29:33
Block: 1127072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283288 RingCT/type: yes/0
Extra: 013ec6aa0ec614bac53874cfe8345bdfb52e4f49c95e75f9324b489b393864ba25021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc5cd01acb73a88d5e90610543baf92e3854834f18a1b4eb754f8a0d5a3d0c5 0.600000000000 1609871 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": 1127082, "vin": [ { "gen": { "height": 1127072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc5cd01acb73a88d5e90610543baf92e3854834f18a1b4eb754f8a0d5a3d0c5" } } ], "extra": [ 1, 62, 198, 170, 14, 198, 20, 186, 197, 56, 116, 207, 232, 52, 91, 223, 181, 46, 79, 73, 201, 94, 117, 249, 50, 75, 72, 155, 57, 56, 100, 186, 37, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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