Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167b64b9f8af3fbefba3638b2c0a855670cf0b1e7de877c99fde3ab661988331

Tx prefix hash: 18b2448338e3d363d71f328462530b10b2d5d1b85e8c720014a014bf3e81440d
Tx public key: 0a8e6322d78d6f27de078728c1512e5ad4f52ad4220307002545d631c12274d9
Timestamp: 1681397112 Timestamp [UCT]: 2023-04-13 14:45:12 Age [y:d:h:m:s]: 02:042:09:32:16
Block: 737754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552496 RingCT/type: yes/0
Extra: 010a8e6322d78d6f27de078728c1512e5ad4f52ad4220307002545d631c12274d9021100000004b3164c24000000000000000000

1 output(s) for total of 2.205540123000 dcy

stealth address amount amount idx
00: ed4cacb1c02eb76e71b5fc633ea361d4c64010c3af0359be9054c0d56887a590 2.205540123000 1184349 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": 737764, "vin": [ { "gen": { "height": 737754 } } ], "vout": [ { "amount": 2205540123, "target": { "key": "ed4cacb1c02eb76e71b5fc633ea361d4c64010c3af0359be9054c0d56887a590" } } ], "extra": [ 1, 10, 142, 99, 34, 215, 141, 111, 39, 222, 7, 135, 40, 193, 81, 46, 90, 212, 245, 42, 212, 34, 3, 7, 0, 37, 69, 214, 49, 193, 34, 116, 217, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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