Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571b5ad4c45bd9d961199c28446580884b3c6f59250d8d3f9e9c811efc2f6824

Tx prefix hash: 46ae7ec1ace6e0c8155ae993dad5c0a047a65a99a0f3970b64dd427d07d0263b
Tx public key: 118e4a9420096de942970a880071168a9314099f43ad7b4060cc31a6bde6a066
Timestamp: 1737804762 Timestamp [UCT]: 2025-01-25 11:32:42 Age [y:d:h:m:s]: 00:143:04:36:42
Block: 1204971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102083 RingCT/type: yes/0
Extra: 01118e4a9420096de942970a880071168a9314099f43ad7b4060cc31a6bde6a066021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d632b63528c41f3a0a117b57528802e93fe9e6c6b68b89581f70c0de65c43b 0.600000000000 1691666 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": 1204981, "vin": [ { "gen": { "height": 1204971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d632b63528c41f3a0a117b57528802e93fe9e6c6b68b89581f70c0de65c43b" } } ], "extra": [ 1, 17, 142, 74, 148, 32, 9, 109, 233, 66, 151, 10, 136, 0, 113, 22, 138, 147, 20, 9, 159, 67, 173, 123, 64, 96, 204, 49, 166, 189, 230, 160, 102, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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