Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0699d8be1ed98c4d614929f29aab70c6e61f97e4c80f93eec7bec84bcbd54d

Tx prefix hash: 057f56a2cc0506b6b04d13e9122972522aa33022bbe47cf20a67298300d497dc
Tx public key: f697fc77e17578c5a2ae201f3b4b4e86094d3e66d5a3027bd1ded0927b36a704
Timestamp: 1761410906 Timestamp [UCT]: 2025-10-25 16:48:26 Age [y:d:h:m:s]: 00:057:22:08:40
Block: 1397768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41458 RingCT/type: yes/0
Extra: 01f697fc77e17578c5a2ae201f3b4b4e86094d3e66d5a3027bd1ded0927b36a704021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e98b1e3fca264e3899fd6c0561b5db1603d2e9a498bef3d7ed829acdffc08f 0.600000000000 1886059 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": 1397778, "vin": [ { "gen": { "height": 1397768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e98b1e3fca264e3899fd6c0561b5db1603d2e9a498bef3d7ed829acdffc08f" } } ], "extra": [ 1, 246, 151, 252, 119, 225, 117, 120, 197, 162, 174, 32, 31, 59, 75, 78, 134, 9, 77, 62, 102, 213, 163, 2, 123, 209, 222, 208, 146, 123, 54, 167, 4, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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