Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0d386565dd0530ca0cad6fcbc32b12e26df9a3557d0760246e18a0cb35c1e2b

Tx prefix hash: 25d4525006b9ac902247a53bfc5063e6744fa72207c918cc95299c7bb99b319b
Tx public key: 51c1d100cf5b6ab42961e0e783d2889057d86d268c1e38a3cf4d9dd316a16e84
Timestamp: 1717732524 Timestamp [UCT]: 2024-06-07 03:55:24 Age [y:d:h:m:s]: 00:321:05:54:47
Block: 1038763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229589 RingCT/type: yes/0
Extra: 0151c1d100cf5b6ab42961e0e783d2889057d86d268c1e38a3cf4d9dd316a16e8402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8624c07c080b8f0d720f99cd7799132a86f79dbde8f04fa18c36d80199da58ba 0.600000000000 1507324 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": 1038773, "vin": [ { "gen": { "height": 1038763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8624c07c080b8f0d720f99cd7799132a86f79dbde8f04fa18c36d80199da58ba" } } ], "extra": [ 1, 81, 193, 209, 0, 207, 91, 106, 180, 41, 97, 224, 231, 131, 210, 136, 144, 87, 216, 109, 38, 140, 30, 56, 163, 207, 77, 157, 211, 22, 161, 110, 132, 2, 17, 0, 0, 0, 1, 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