Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b104190458a209a3f495514ef97fb74b4ef33b4f3f4fa0d9719da20b9c3934

Tx prefix hash: 770c80c87bd28ff1d8077070652a585a56d15ecbfa0d886b927ac23c0cba613b
Tx public key: 55f3e7b205d3a32072c405f016b1601c46140e58e67a22bddc3255197bec3e9c
Timestamp: 1731448366 Timestamp [UCT]: 2024-11-12 21:52:46 Age [y:d:h:m:s]: 00:142:17:09:17
Block: 1152375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101828 RingCT/type: yes/0
Extra: 0155f3e7b205d3a32072c405f016b1601c46140e58e67a22bddc3255197bec3e9c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11c8e118e7a02ad4ef4bdd5c9cd784fe01a7c62f2cb01d3a80c1da3257bbecdc 0.600000000000 1637972 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": 1152385, "vin": [ { "gen": { "height": 1152375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c8e118e7a02ad4ef4bdd5c9cd784fe01a7c62f2cb01d3a80c1da3257bbecdc" } } ], "extra": [ 1, 85, 243, 231, 178, 5, 211, 163, 32, 114, 196, 5, 240, 22, 177, 96, 28, 70, 20, 14, 88, 230, 122, 34, 189, 220, 50, 85, 25, 123, 236, 62, 156, 2, 17, 0, 0, 0, 2, 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