Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167f8c36529013c5d6261e45160988d3f2c21563b104ef532968ef83833978a4

Tx prefix hash: 95eb7a0870017fcb49c3fa249b9940bfde3d1603bff005655015a2e1edc4b62a
Tx public key: 263781bee4f3baf9d8dae40b6f4cd86edd87f00819699a45f258b4017589f2e6
Timestamp: 1581957325 Timestamp [UCT]: 2020-02-17 16:35:25 Age [y:d:h:m:s]: 04:263:07:11:59
Block: 66983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080429 RingCT/type: yes/0
Extra: 01263781bee4f3baf9d8dae40b6f4cd86edd87f00819699a45f258b4017589f2e60211000000018a2ee0d9000000000000000000

1 output(s) for total of 368.178414467000 dcy

stealth address amount amount idx
00: 453f4afc99276df0a20e3936bef39fbf2e833bf00da22552d30f4a95ad540305 368.178414467000 123322 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": 66993, "vin": [ { "gen": { "height": 66983 } } ], "vout": [ { "amount": 368178414467, "target": { "key": "453f4afc99276df0a20e3936bef39fbf2e833bf00da22552d30f4a95ad540305" } } ], "extra": [ 1, 38, 55, 129, 190, 228, 243, 186, 249, 216, 218, 228, 11, 111, 76, 216, 110, 221, 135, 240, 8, 25, 105, 154, 69, 242, 88, 180, 1, 117, 137, 242, 230, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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