Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a042cd5c92680e7443ed62387631ab54663e802e8c72874b1c7854c07b9a81

Tx prefix hash: 39859d9a29ba232af0e813189765dc691041b3626ae3fe83b61a4be78f77d101
Tx public key: 8dd5df7f06c3f820dce39ce4e0f3efc92736377dc2034a59f8809c96e62dc6ef
Timestamp: 1752737988 Timestamp [UCT]: 2025-07-17 07:39:48 Age [y:d:h:m:s]: 00:120:01:12:38
Block: 1327264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84576 RingCT/type: yes/0
Extra: 018dd5df7f06c3f820dce39ce4e0f3efc92736377dc2034a59f8809c96e62dc6ef02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86acc8761e1152b09b029d842b34623973cfdc02e2484ddc1981e2699c224a2c 0.600000000000 1815017 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": 1327274, "vin": [ { "gen": { "height": 1327264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86acc8761e1152b09b029d842b34623973cfdc02e2484ddc1981e2699c224a2c" } } ], "extra": [ 1, 141, 213, 223, 127, 6, 195, 248, 32, 220, 227, 156, 228, 224, 243, 239, 201, 39, 54, 55, 125, 194, 3, 74, 89, 248, 128, 156, 150, 230, 45, 198, 239, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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