Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d76829eea205f1a7f700c50b083cf7a736b9f96ebbe9252e42f0e413f7feec

Tx prefix hash: dd922eb815234350ae95104be04a082b9c516657edf27653e208e08204bcad52
Tx public key: e767dd6513f3ffb7ebe4d56192c0f1e842a4f7328f240468983416b7cf252100
Timestamp: 1584760408 Timestamp [UCT]: 2020-03-21 03:13:28 Age [y:d:h:m:s]: 05:228:21:26:53
Block: 85991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318436 RingCT/type: yes/0
Extra: 01e767dd6513f3ffb7ebe4d56192c0f1e842a4f7328f240468983416b7cf252100021100000006c2c2f844000000000000000000

1 output(s) for total of 318.497430544000 dcy

stealth address amount amount idx
00: aa989f0226322f7f61592294ecf21f1d3b10b95d7a2181efa8e3bdae9c333c07 318.497430544000 155247 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": 86001, "vin": [ { "gen": { "height": 85991 } } ], "vout": [ { "amount": 318497430544, "target": { "key": "aa989f0226322f7f61592294ecf21f1d3b10b95d7a2181efa8e3bdae9c333c07" } } ], "extra": [ 1, 231, 103, 221, 101, 19, 243, 255, 183, 235, 228, 213, 97, 146, 192, 241, 232, 66, 164, 247, 50, 143, 36, 4, 104, 152, 52, 22, 183, 207, 37, 33, 0, 2, 17, 0, 0, 0, 6, 194, 194, 248, 68, 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