Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8da4e6bc61cf1de8e8484e6502e66e840220f1c03a65841e5d37af7e3d62c456

Tx prefix hash: 4b66b1adab46125b2561ef29f656b0a9f5549c4dcda58bdaa5e030b400feaa01
Tx public key: a523021b1868d6c792f5de43d3835cc3c80fe9941f5f31160d431c7e0fedaca2
Timestamp: 1732620962 Timestamp [UCT]: 2024-11-26 11:36:02 Age [y:d:h:m:s]: 01:063:18:38:11
Block: 1162087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303911 RingCT/type: yes/0
Extra: 01a523021b1868d6c792f5de43d3835cc3c80fe9941f5f31160d431c7e0fedaca2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70b0a5b61859a7cfdeab2f94ecf36e97718e496b4a7c6e9437ddf2d893b6c8f7 0.600000000000 1647742 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": 1162097, "vin": [ { "gen": { "height": 1162087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70b0a5b61859a7cfdeab2f94ecf36e97718e496b4a7c6e9437ddf2d893b6c8f7" } } ], "extra": [ 1, 165, 35, 2, 27, 24, 104, 214, 199, 146, 245, 222, 67, 211, 131, 92, 195, 200, 15, 233, 148, 31, 95, 49, 22, 13, 67, 28, 126, 15, 237, 172, 162, 2, 17, 0, 0, 0, 1, 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