Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a478891f0fade2348d3fa16462e5094e860c1bbf62517c238037036fabc0d84

Tx prefix hash: 4375c9facc579df4e3f1dd781cbca0ed8849ea414ec6967c7ec268bca934ae87
Tx public key: 55c898ea4fc51e5d64171d7c0cf6cdd290326c36c8f1eeda5dcede5ba557b94b
Timestamp: 1740362840 Timestamp [UCT]: 2025-02-24 02:07:20 Age [y:d:h:m:s]: 00:016:15:09:40
Block: 1225906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11926 RingCT/type: yes/0
Extra: 0155c898ea4fc51e5d64171d7c0cf6cdd290326c36c8f1eeda5dcede5ba557b94b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72b37bcb5727945c19a37d0740771c41e0a07183f177f9c545e409b8a7043897 0.600000000000 1712777 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": 1225916, "vin": [ { "gen": { "height": 1225906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72b37bcb5727945c19a37d0740771c41e0a07183f177f9c545e409b8a7043897" } } ], "extra": [ 1, 85, 200, 152, 234, 79, 197, 30, 93, 100, 23, 29, 124, 12, 246, 205, 210, 144, 50, 108, 54, 200, 241, 238, 218, 93, 206, 222, 91, 165, 87, 185, 75, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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