Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296672f805878bd6dad205c2e3943ba1c3568a74db6ae5962c4f16df7ae99ca2

Tx prefix hash: 37e3e5538a442a2724afd8107f053a3704c7dc08f61dff1d78fafaca4d0a260d
Tx public key: f0561a35636ae36fbdc68f908499b9d96db897d4325df8b598b335e568394f96
Timestamp: 1582293816 Timestamp [UCT]: 2020-02-21 14:03:36 Age [y:d:h:m:s]: 05:257:14:31:49
Block: 69582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334971 RingCT/type: yes/0
Extra: 01f0561a35636ae36fbdc68f908499b9d96db897d4325df8b598b335e568394f96021100000001c71d3ff9000000000000000000

1 output(s) for total of 360.949756715000 dcy

stealth address amount amount idx
00: d1535ed99af144d389d51b87f2c6c0783450aa166927688b3474c2aaae8fcfab 360.949756715000 128325 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": 69592, "vin": [ { "gen": { "height": 69582 } } ], "vout": [ { "amount": 360949756715, "target": { "key": "d1535ed99af144d389d51b87f2c6c0783450aa166927688b3474c2aaae8fcfab" } } ], "extra": [ 1, 240, 86, 26, 53, 99, 106, 227, 111, 189, 198, 143, 144, 132, 153, 185, 217, 109, 184, 151, 212, 50, 93, 248, 181, 152, 179, 53, 229, 104, 57, 79, 150, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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