Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aafa7a6a7b1097c839bed589fd018f87e3594832bb074717c3bcd0ac0cfe8c8

Tx prefix hash: d675bce283da351eeac80fffdf3ae83fd03995f976f1a9a0e7332b7fdf9fc2ff
Tx public key: 765177799d7ff016bd429efeb793c82785e0efecd7e51ebdc9a5050150513fb2
Timestamp: 1673457910 Timestamp [UCT]: 2023-01-11 17:25:10 Age [y:d:h:m:s]: 02:045:22:08:02
Block: 672561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554465 RingCT/type: yes/0
Extra: 01765177799d7ff016bd429efeb793c82785e0efecd7e51ebdc9a5050150513fb202110000000352542ceb000000000000000000

1 output(s) for total of 3.626821379000 dcy

stealth address amount amount idx
00: f716b420f4cc6a25b76c448d1324edb42d70cafb27bcd3e9e5fa61299187c7e8 3.626821379000 1114118 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": 672571, "vin": [ { "gen": { "height": 672561 } } ], "vout": [ { "amount": 3626821379, "target": { "key": "f716b420f4cc6a25b76c448d1324edb42d70cafb27bcd3e9e5fa61299187c7e8" } } ], "extra": [ 1, 118, 81, 119, 121, 157, 127, 240, 22, 189, 66, 158, 254, 183, 147, 200, 39, 133, 224, 239, 236, 215, 229, 30, 189, 201, 165, 5, 1, 80, 81, 63, 178, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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