Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b41c3790509f860d1302d155d05b6cd4df3afa1cb667a54a1e0660a3909498d

Tx prefix hash: 5f587717cc5910c18549f889fd80be5b1d3750708e0d1ab82a899a18e8939e69
Tx public key: 7cd3cb55aab7b1f4347a6c7bac0cc304cee7dc8ac0a32b641dcf0940a5a05d90
Timestamp: 1688339466 Timestamp [UCT]: 2023-07-02 23:11:06 Age [y:d:h:m:s]: 01:136:03:58:11
Block: 795339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358620 RingCT/type: yes/0
Extra: 017cd3cb55aab7b1f4347a6c7bac0cc304cee7dc8ac0a32b641dcf0940a5a05d900211000000024b8f5122000000000000000000

1 output(s) for total of 1.421385461000 dcy

stealth address amount amount idx
00: ae40179ea03c5059829139a637c9c5bcf6d15ee1999890674108991eb37c67e0 1.421385461000 1246140 of 0

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": 795349, "vin": [ { "gen": { "height": 795339 } } ], "vout": [ { "amount": 1421385461, "target": { "key": "ae40179ea03c5059829139a637c9c5bcf6d15ee1999890674108991eb37c67e0" } } ], "extra": [ 1, 124, 211, 203, 85, 170, 183, 177, 244, 52, 122, 108, 123, 172, 12, 195, 4, 206, 231, 220, 138, 192, 163, 43, 100, 29, 207, 9, 64, 165, 160, 93, 144, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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