Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f231c2fbccead348e278e3b9759c06ee7f5d11cf46c3c4af9badf0ccdafd6d7f

Tx prefix hash: d72ddf25f8cd15f3624fc5314158b3d321c3c255c4d4e39e5ec6a42fd64ad527
Tx public key: a7b2010d5acfe5be3dc1e1e6e8cf1a189718d9a5d623eb6454e9d9e4754c5abd
Timestamp: 1751476111 Timestamp [UCT]: 2025-07-02 17:08:31 Age [y:d:h:m:s]: 00:131:00:13:14
Block: 1317363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91859 RingCT/type: yes/0
Extra: 01a7b2010d5acfe5be3dc1e1e6e8cf1a189718d9a5d623eb6454e9d9e4754c5abd021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cedfaab65c39ca91349f389dc3dde3358bea0012039d15a9a0d72aaf570fd39a 0.600000000000 1805030 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": 1317373, "vin": [ { "gen": { "height": 1317363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cedfaab65c39ca91349f389dc3dde3358bea0012039d15a9a0d72aaf570fd39a" } } ], "extra": [ 1, 167, 178, 1, 13, 90, 207, 229, 190, 61, 193, 225, 230, 232, 207, 26, 24, 151, 24, 217, 165, 214, 35, 235, 100, 84, 233, 217, 228, 117, 76, 90, 189, 2, 17, 0, 0, 0, 4, 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