Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f7d78565b1446cf9fb100b54f5648c0e7620309c4f7bac240382610b170079

Tx prefix hash: 3b65f2c85447f476a4dbd244d5ed49bb6a071c21af82d05f7ca8e7db353f0bcf
Tx public key: 62a3944908390f595950c85f1c1e428956b6e3d9e50703dd502a3b3a1e56325a
Timestamp: 1742551652 Timestamp [UCT]: 2025-03-21 10:07:32 Age [y:d:h:m:s]: 00:077:22:02:19
Block: 1244054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55728 RingCT/type: yes/0
Extra: 0162a3944908390f595950c85f1c1e428956b6e3d9e50703dd502a3b3a1e56325a021100000002bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cfb461dc644e279c39e1bbddcfc218c79e9d202601f9cca81fcf00d9052353a 0.600000000000 1731045 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": 1244064, "vin": [ { "gen": { "height": 1244054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cfb461dc644e279c39e1bbddcfc218c79e9d202601f9cca81fcf00d9052353a" } } ], "extra": [ 1, 98, 163, 148, 73, 8, 57, 15, 89, 89, 80, 200, 95, 28, 30, 66, 137, 86, 182, 227, 217, 229, 7, 3, 221, 80, 42, 59, 58, 30, 86, 50, 90, 2, 17, 0, 0, 0, 2, 191, 167, 118, 35, 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