Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 910bf3ae81283b1e663f00cbc17b4c58da67aa19706d9d31bde4cfef27401ea4

Tx prefix hash: b1ecb7296b86cf3688cdce60d6b64b621bab005cc47ef71c4c87d97aedcaa814
Tx public key: bd563e04b4c7d82c3d411e24a5fa0351da1ae416d108134e7472f619f3ad0e8b
Timestamp: 1686009337 Timestamp [UCT]: 2023-06-05 23:55:37 Age [y:d:h:m:s]: 02:154:14:36:22
Block: 775996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 630262 RingCT/type: yes/0
Extra: 01bd563e04b4c7d82c3d411e24a5fa0351da1ae416d108134e7472f619f3ad0e8b021100000002faf35c9c000000000000000000

1 output(s) for total of 1.647416023000 dcy

stealth address amount amount idx
00: d49661d96f355599d8ba62a710229f29e40ae6f0339b9206ce290f1bd9c7bb43 1.647416023000 1225527 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": 776006, "vin": [ { "gen": { "height": 775996 } } ], "vout": [ { "amount": 1647416023, "target": { "key": "d49661d96f355599d8ba62a710229f29e40ae6f0339b9206ce290f1bd9c7bb43" } } ], "extra": [ 1, 189, 86, 62, 4, 180, 199, 216, 44, 61, 65, 30, 36, 165, 250, 3, 81, 218, 26, 228, 22, 209, 8, 19, 78, 116, 114, 246, 25, 243, 173, 14, 139, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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