Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2f12b45b6578ebf49e31a0c489786aeb8a3df5c1885e96164400ef51988ea2

Tx prefix hash: c555b6fa68cc8d2e0f0e7534073504448455f3d12dade5d3be790ce92367d20e
Tx public key: 5b8bc6a535e0b63b1581673fa77a2502c948d7acfec6ea9dffe6cb44ad3e9bd1
Timestamp: 1760439735 Timestamp [UCT]: 2025-10-14 11:02:15 Age [y:d:h:m:s]: 00:043:23:02:18
Block: 1389701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31479 RingCT/type: yes/0
Extra: 015b8bc6a535e0b63b1581673fa77a2502c948d7acfec6ea9dffe6cb44ad3e9bd10211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2903c80217365f526f2e6c903cadbd759e2392bb056f09c78d067158c421a20 0.600000000000 1877930 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": 1389711, "vin": [ { "gen": { "height": 1389701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2903c80217365f526f2e6c903cadbd759e2392bb056f09c78d067158c421a20" } } ], "extra": [ 1, 91, 139, 198, 165, 53, 224, 182, 59, 21, 129, 103, 63, 167, 122, 37, 2, 201, 72, 215, 172, 254, 198, 234, 157, 255, 230, 203, 68, 173, 62, 155, 209, 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