Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401cc2e46e8705002ba1b68610018c893ac3ed19f44d9eba217f52849f68573f

Tx prefix hash: 47e03d90d9722f1574ec8f837fc02a230c3af1af74a7bae0373edb85327b8fc2
Tx public key: 663dcb67f1d12e1ab76b4846f29221e619f1269d91d5823c833970e6c2bb018b
Timestamp: 1735635259 Timestamp [UCT]: 2024-12-31 08:54:19 Age [y:d:h:m:s]: 00:117:04:21:30
Block: 1187050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83557 RingCT/type: yes/0
Extra: 01663dcb67f1d12e1ab76b4846f29221e619f1269d91d5823c833970e6c2bb018b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efb25690ec8b023909757823a46347294e4c556cbd3fb72a4da9c4259fa6bf21 0.600000000000 1673537 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": 1187060, "vin": [ { "gen": { "height": 1187050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efb25690ec8b023909757823a46347294e4c556cbd3fb72a4da9c4259fa6bf21" } } ], "extra": [ 1, 102, 61, 203, 103, 241, 209, 46, 26, 183, 107, 72, 70, 242, 146, 33, 230, 25, 241, 38, 157, 145, 213, 130, 60, 131, 57, 112, 230, 194, 187, 1, 139, 2, 17, 0, 0, 0, 3, 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