Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64294573021224693a026ade8c10e27cbaccfedd4fbb17360ad1fda60ce11d19

Tx prefix hash: 6b1e5cd9188397cd3edf3b57f43d7a0824a72ce5c08030982866088900517953
Tx public key: 21e0571ff08f949ee96eb91f7d9ae0c548bb59de6db0cb1e772bc6c1e7ea730d
Timestamp: 1754283019 Timestamp [UCT]: 2025-08-04 04:50:19 Age [y:d:h:m:s]: 00:064:21:58:25
Block: 1339877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45273 RingCT/type: yes/0
Extra: 0121e0571ff08f949ee96eb91f7d9ae0c548bb59de6db0cb1e772bc6c1e7ea730d021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6537e9f502ea9a45d7d63722ec8ea8b1e50d75385fd548b98f53f5900e0b8a74 0.600000000000 1827692 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": 1339887, "vin": [ { "gen": { "height": 1339877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6537e9f502ea9a45d7d63722ec8ea8b1e50d75385fd548b98f53f5900e0b8a74" } } ], "extra": [ 1, 33, 224, 87, 31, 240, 143, 148, 158, 233, 110, 185, 31, 125, 154, 224, 197, 72, 187, 89, 222, 109, 176, 203, 30, 119, 43, 198, 193, 231, 234, 115, 13, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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