Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5df511c0266f947cc9fcf0de3a49e506a4f5975df1762739282d9ec12b932548

Tx prefix hash: f6057bbe689f61541340768d7abe6c404719d2ec1f46adaf695c7e448d8b198b
Tx public key: 589bb14d3d56f5bdef66b6244650e7f9a06aafa2f169dd99021c7c66d17576b9
Timestamp: 1576133318 Timestamp [UCT]: 2019-12-12 06:48:38 Age [y:d:h:m:s]: 05:071:14:02:57
Block: 26062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196823 RingCT/type: yes/0
Extra: 01589bb14d3d56f5bdef66b6244650e7f9a06aafa2f169dd99021c7c66d17576b902110000000fad433a0b000000000000000000

1 output(s) for total of 503.091110141000 dcy

stealth address amount amount idx
00: cea71912c50c0e21cbf37ae731a84c6b9d62a73fcd51ea0201110e34e03110a4 503.091110141000 43017 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": 26072, "vin": [ { "gen": { "height": 26062 } } ], "vout": [ { "amount": 503091110141, "target": { "key": "cea71912c50c0e21cbf37ae731a84c6b9d62a73fcd51ea0201110e34e03110a4" } } ], "extra": [ 1, 88, 155, 177, 77, 61, 86, 245, 189, 239, 102, 182, 36, 70, 80, 231, 249, 160, 106, 175, 162, 241, 105, 221, 153, 2, 28, 124, 102, 209, 117, 118, 185, 2, 17, 0, 0, 0, 15, 173, 67, 58, 11, 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