Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779700f903aa23c7bf321c46adcf6ce0cc002a9cdb16a21abd8fe90207f7cb5e

Tx prefix hash: bae0b14efeccbdb1b38c22bf46295c41f08fc58c9bde5de58756a780f43fefa1
Tx public key: 280c393d2b7fe17c8762024fc4ff989dbc86b2c816b5847f36e35e6eca413c71
Timestamp: 1582098259 Timestamp [UCT]: 2020-02-19 07:44:19 Age [y:d:h:m:s]: 04:321:19:51:11
Block: 67915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122559 RingCT/type: yes/0
Extra: 01280c393d2b7fe17c8762024fc4ff989dbc86b2c816b5847f36e35e6eca413c710211000000010aca7173000000000000000000

1 output(s) for total of 365.569722332000 dcy

stealth address amount amount idx
00: 0daa5cb21020df940924a027dd0dff8a9ec56a4ff5ab851be5507478ea3f2868 365.569722332000 125131 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": 67925, "vin": [ { "gen": { "height": 67915 } } ], "vout": [ { "amount": 365569722332, "target": { "key": "0daa5cb21020df940924a027dd0dff8a9ec56a4ff5ab851be5507478ea3f2868" } } ], "extra": [ 1, 40, 12, 57, 61, 43, 127, 225, 124, 135, 98, 2, 79, 196, 255, 152, 157, 188, 134, 178, 200, 22, 181, 132, 127, 54, 227, 94, 110, 202, 65, 60, 113, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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