Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a14306e8c7d8e62055c2de30bb5958ba9281d0acc8f243ca1514be7ea679c12

Tx prefix hash: f668791dee5df6b0a91b1060c03533d8924f096afbec865a56cbf531376105bc
Tx public key: 04b2105470395b742eb7b4b7b40aafea76b7666285cf0f16e56e069d9aec7a21
Timestamp: 1703382043 Timestamp [UCT]: 2023-12-24 01:40:43 Age [y:d:h:m:s]: 01:158:01:59:40
Block: 919779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374149 RingCT/type: yes/0
Extra: 0104b2105470395b742eb7b4b7b40aafea76b7666285cf0f16e56e069d9aec7a210211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c683aebfaefa8bff3daaa5cacec6d5c2519968c0cf1cabfd73e2cf729145176 0.600000000000 1377457 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": 919789, "vin": [ { "gen": { "height": 919779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c683aebfaefa8bff3daaa5cacec6d5c2519968c0cf1cabfd73e2cf729145176" } } ], "extra": [ 1, 4, 178, 16, 84, 112, 57, 91, 116, 46, 183, 180, 183, 180, 10, 175, 234, 118, 183, 102, 98, 133, 207, 15, 22, 229, 110, 6, 157, 154, 236, 122, 33, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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