Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a1a645699734d1aedb1ad6d99e4228f215cbfa8b92f066a03a605b107b9d1d

Tx prefix hash: 3f9a8e8b558701e63d7422131b36f56681727aeb4a3e8c1e925768303d7de1c5
Tx public key: 7ec606a4e361ece8f278607b12211e68f6cf9fa6b609ad22b2d600293a27a0f4
Timestamp: 1734216426 Timestamp [UCT]: 2024-12-14 22:47:06 Age [y:d:h:m:s]: 00:100:10:44:44
Block: 1175324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71558 RingCT/type: yes/0
Extra: 017ec606a4e361ece8f278607b12211e68f6cf9fa6b609ad22b2d600293a27a0f40211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 426f2034064abe8433a8c967120157041b3b38bca135a503fc4b41c5109674a2 0.600000000000 1661589 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": 1175334, "vin": [ { "gen": { "height": 1175324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "426f2034064abe8433a8c967120157041b3b38bca135a503fc4b41c5109674a2" } } ], "extra": [ 1, 126, 198, 6, 164, 227, 97, 236, 232, 242, 120, 96, 123, 18, 33, 30, 104, 246, 207, 159, 166, 182, 9, 173, 34, 178, 214, 0, 41, 58, 39, 160, 244, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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