Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8559bb65a3b48d826f510f702e0db4d68a3fdb2e8b317c9bed7f144ddd61549

Tx prefix hash: f441a94d688e5895913634dc160e34d27dcf4968c01e8f5d2144b8562654920d
Tx public key: 870f29afc3b4fb6ac76ae4e2cf1bd0168040fbad0f853e66a756e34d7d1d549f
Timestamp: 1754736891 Timestamp [UCT]: 2025-08-09 10:54:51 Age [y:d:h:m:s]: 00:053:08:18:02
Block: 1343435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37192 RingCT/type: yes/0
Extra: 01870f29afc3b4fb6ac76ae4e2cf1bd0168040fbad0f853e66a756e34d7d1d549f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b50463169c48b7f33d82e4060336f79e11a0c6a2036326cc76046741b0d9777 0.600000000000 1831274 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": 1343445, "vin": [ { "gen": { "height": 1343435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b50463169c48b7f33d82e4060336f79e11a0c6a2036326cc76046741b0d9777" } } ], "extra": [ 1, 135, 15, 41, 175, 195, 180, 251, 106, 199, 106, 228, 226, 207, 27, 208, 22, 128, 64, 251, 173, 15, 133, 62, 102, 167, 86, 227, 77, 125, 29, 84, 159, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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