Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4de4e01e36e570b8f5df1db2a5f4e7d3a5d74662d9c7820eb439c1f23d8e255

Tx prefix hash: 497cb882f2c65d141b8ae5af5130e3731e7ddf0c92e9c990ef0c5dec40d4c9de
Tx public key: 80c4b17d7881ed508706154f1e64b33284cbc1fc9f496dfcd8acad3216fe345a
Timestamp: 1694243468 Timestamp [UCT]: 2023-09-09 07:11:08 Age [y:d:h:m:s]: 01:167:08:44:43
Block: 844204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380672 RingCT/type: yes/0
Extra: 0180c4b17d7881ed508706154f1e64b33284cbc1fc9f496dfcd8acad3216fe345a02110000000933af99f4000000000000000000

1 output(s) for total of 0.979043002000 dcy

stealth address amount amount idx
00: dfdd12d093b90b484f4e9a681a1611ae51b0780d3be47ee5c46d1c995aee12a6 0.979043002000 1297498 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": 844214, "vin": [ { "gen": { "height": 844204 } } ], "vout": [ { "amount": 979043002, "target": { "key": "dfdd12d093b90b484f4e9a681a1611ae51b0780d3be47ee5c46d1c995aee12a6" } } ], "extra": [ 1, 128, 196, 177, 125, 120, 129, 237, 80, 135, 6, 21, 79, 30, 100, 179, 50, 132, 203, 193, 252, 159, 73, 109, 252, 216, 172, 173, 50, 22, 254, 52, 90, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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