Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a653e81cede8bfa194cc3aff93cf3f1cec4a98e8a9ec53f7562f6a5579c8742

Tx prefix hash: 6c0f82a580a401f248cba8106c41d7622bb89444dfe3ef1b14feafab3fd73594
Tx public key: 2001ce8a7bd6c0c4516476bbc1c7668091da63a041c054cd2e907923fcb426a3
Timestamp: 1712325957 Timestamp [UCT]: 2024-04-05 14:05:57 Age [y:d:h:m:s]: 01:208:19:16:29
Block: 993905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407938 RingCT/type: yes/0
Extra: 012001ce8a7bd6c0c4516476bbc1c7668091da63a041c054cd2e907923fcb426a302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 226f20a0b59ed7ebaaf3b77c0c9a7c09506ba9c9211aacb4ffcdc2d7c355f017 0.600000000000 1454301 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": 993915, "vin": [ { "gen": { "height": 993905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "226f20a0b59ed7ebaaf3b77c0c9a7c09506ba9c9211aacb4ffcdc2d7c355f017" } } ], "extra": [ 1, 32, 1, 206, 138, 123, 214, 192, 196, 81, 100, 118, 187, 193, 199, 102, 128, 145, 218, 99, 160, 65, 192, 84, 205, 46, 144, 121, 35, 252, 180, 38, 163, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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