Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a8ba6c1fbf4cfd047906a9ec1d671e0f96add3bc95e48d7f0a74402077f3d9e

Tx prefix hash: ef63fe76201e169b4c522106e2ab628f4f9f137220715bb10ffcd092e147bae4
Tx public key: 364bd03552023357a40096ee9a56c8c70b520a1a6cca67bf4851d4d39d95bad0
Timestamp: 1702926547 Timestamp [UCT]: 2023-12-18 19:09:07 Age [y:d:h:m:s]: 01:070:11:56:20
Block: 916007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311474 RingCT/type: yes/0
Extra: 01364bd03552023357a40096ee9a56c8c70b520a1a6cca67bf4851d4d39d95bad002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79e6facd6f26355925e0deb0fd1b7d3ffdb0f263ef5a4ce1ea1f7227367fc92c 0.600000000000 1373443 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": 916017, "vin": [ { "gen": { "height": 916007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79e6facd6f26355925e0deb0fd1b7d3ffdb0f263ef5a4ce1ea1f7227367fc92c" } } ], "extra": [ 1, 54, 75, 208, 53, 82, 2, 51, 87, 164, 0, 150, 238, 154, 86, 200, 199, 11, 82, 10, 26, 108, 202, 103, 191, 72, 81, 212, 211, 157, 149, 186, 208, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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