Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94349e7aea2f3f681dd8c2f0a23a8103253005134ecf9d1da5cfc9df54b32222

Tx prefix hash: 118f21c8803e479b4f886b427f7f71bb8c263fdb4e3dd248b767425acabdcc5b
Tx public key: 8727d8a0cff07c34d55ae5018d51ac12b8115da48f2faccf1ba11064541262e8
Timestamp: 1733396384 Timestamp [UCT]: 2024-12-05 10:59:44 Age [y:d:h:m:s]: 00:111:03:34:19
Block: 1168513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79222 RingCT/type: yes/0
Extra: 018727d8a0cff07c34d55ae5018d51ac12b8115da48f2faccf1ba11064541262e8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 215b458774bf4b5e76596428d0b699b31a0e27a5bb4d911d8e894147243df303 0.600000000000 1654222 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": 1168523, "vin": [ { "gen": { "height": 1168513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "215b458774bf4b5e76596428d0b699b31a0e27a5bb4d911d8e894147243df303" } } ], "extra": [ 1, 135, 39, 216, 160, 207, 240, 124, 52, 213, 90, 229, 1, 141, 81, 172, 18, 184, 17, 93, 164, 143, 47, 172, 207, 27, 161, 16, 100, 84, 18, 98, 232, 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