Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df100b95614cc1419ca3afa85a5f903d3ff350cb33b783a0fbab7e11cc33cc44

Tx prefix hash: 53c8c92ec788cd51390f434ac88f7e23e93862819a82c22ff1bfa612fb6e76df
Tx public key: bdcd7bf4d8f09ae0596568a9842aafe9beff15f8be459494d3f23127d029401a
Timestamp: 1608145693 Timestamp [UCT]: 2020-12-16 19:08:13 Age [y:d:h:m:s]: 04:138:19:51:05
Block: 163339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111597 RingCT/type: yes/0
Extra: 01bdcd7bf4d8f09ae0596568a9842aafe9beff15f8be459494d3f23127d029401a02110000000adf1e48bb000000000000000000

1 output(s) for total of 176.521767455000 dcy

stealth address amount amount idx
00: b2d3c35b93421a388c07896122af2c267a7c593f8f00024765391cb5eb8c4be9 176.521767455000 292980 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": 163349, "vin": [ { "gen": { "height": 163339 } } ], "vout": [ { "amount": 176521767455, "target": { "key": "b2d3c35b93421a388c07896122af2c267a7c593f8f00024765391cb5eb8c4be9" } } ], "extra": [ 1, 189, 205, 123, 244, 216, 240, 154, 224, 89, 101, 104, 169, 132, 42, 175, 233, 190, 255, 21, 248, 190, 69, 148, 148, 211, 242, 49, 39, 208, 41, 64, 26, 2, 17, 0, 0, 0, 10, 223, 30, 72, 187, 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