Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84c9fc2f03c6d6b9d45bb689a51be770aeb275867b469cd6b3e1635d010b6872

Tx prefix hash: 20d2c1375ece26f2bd72d969053a774ad8d35ea0fb4bb9b2fa0f6ad678e65374
Tx public key: 16ec4fedf1f0d47cd56b44581c5e5ea5bd3dc98f1cd0aacea3783d14906ad9ff
Timestamp: 1745470809 Timestamp [UCT]: 2025-04-24 05:00:09 Age [y:d:h:m:s]: 00:018:15:27:16
Block: 1268206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13335 RingCT/type: yes/0
Extra: 0116ec4fedf1f0d47cd56b44581c5e5ea5bd3dc98f1cd0aacea3783d14906ad9ff0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 249c20376f74d74ef0981c64bf3a92a578d9faeb153903fff5dc267d90f9dedf 0.600000000000 1755435 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": 1268216, "vin": [ { "gen": { "height": 1268206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "249c20376f74d74ef0981c64bf3a92a578d9faeb153903fff5dc267d90f9dedf" } } ], "extra": [ 1, 22, 236, 79, 237, 241, 240, 212, 124, 213, 107, 68, 88, 28, 94, 94, 165, 189, 61, 201, 143, 28, 208, 170, 206, 163, 120, 61, 20, 144, 106, 217, 255, 2, 17, 0, 0, 0, 3, 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