Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e352a84359ee86a767402d9ea0c2a976a670145c0b9b8b9b294c5b73a50ae97a

Tx prefix hash: 5c0958a83eefbedd16b06ebc8b1f0ccabfcd309de577459273f4a46a8cb87822
Tx public key: dc67509bf88f30e64950c4aef0b045464396b50d5ca14a0b86b4136a13c8b0d4
Timestamp: 1750783857 Timestamp [UCT]: 2025-06-24 16:50:57 Age [y:d:h:m:s]: 00:217:20:31:49
Block: 1311939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153558 RingCT/type: yes/0
Extra: 01dc67509bf88f30e64950c4aef0b045464396b50d5ca14a0b86b4136a13c8b0d40211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ef45536745ba1ac41875bcbac4530be8431bca6a15dcf16cbd8a87ad5a6025f 0.600000000000 1799568 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": 1311949, "vin": [ { "gen": { "height": 1311939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef45536745ba1ac41875bcbac4530be8431bca6a15dcf16cbd8a87ad5a6025f" } } ], "extra": [ 1, 220, 103, 80, 155, 248, 143, 48, 230, 73, 80, 196, 174, 240, 176, 69, 70, 67, 150, 181, 13, 92, 161, 74, 11, 134, 180, 19, 106, 19, 200, 176, 212, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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