Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53cb4d57ad28e3d0be40c8469c49dd03702cad03d7938f4ed24a7c48fb1a1a33

Tx prefix hash: 2719994bc35dc815f3ac711450f8c739724fc9380c12c1ccff45e142f6cadcfe
Tx public key: 0ebe2165ff0fae801efe270ea8c0417b4ed0d7b70ced92af48e864dd4af6c40a
Timestamp: 1699857822 Timestamp [UCT]: 2023-11-13 06:43:42 Age [y:d:h:m:s]: 01:364:01:42:17
Block: 890570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519104 RingCT/type: yes/0
Extra: 010ebe2165ff0fae801efe270ea8c0417b4ed0d7b70ced92af48e864dd4af6c40a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.687340436000 dcy

stealth address amount amount idx
00: ea5c63d08d5fe1643e81bd3a4847f64d2ec13b79908e9008325d07ddd1343479 0.687340436000 1346593 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": 890580, "vin": [ { "gen": { "height": 890570 } } ], "vout": [ { "amount": 687340436, "target": { "key": "ea5c63d08d5fe1643e81bd3a4847f64d2ec13b79908e9008325d07ddd1343479" } } ], "extra": [ 1, 14, 190, 33, 101, 255, 15, 174, 128, 30, 254, 39, 14, 168, 192, 65, 123, 78, 208, 215, 183, 12, 237, 146, 175, 72, 232, 100, 221, 74, 246, 196, 10, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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