Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50cee9bc68d2b3bfae9d5e1ac25f3fddaecb2a3b0d0a45d365681dcee49eed00

Tx prefix hash: af0aca76f36a6446d34098da9a8a111efa4360a85eda3bb8375be450e251f29e
Tx public key: f82c109bb2c2a55ee5e8d4daef3e6ad0d56977396bd0f0c7ce8b0cec31faa001
Timestamp: 1731994897 Timestamp [UCT]: 2024-11-19 05:41:37 Age [y:d:h:m:s]: 00:156:09:09:09
Block: 1156906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111597 RingCT/type: yes/0
Extra: 01f82c109bb2c2a55ee5e8d4daef3e6ad0d56977396bd0f0c7ce8b0cec31faa001021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a3c861cf2d6bf78316484ac00409b3717118c80da5c2a445d016b3a9fc339c 0.600000000000 1642529 of 15

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": 1156916, "vin": [ { "gen": { "height": 1156906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a3c861cf2d6bf78316484ac00409b3717118c80da5c2a445d016b3a9fc339c" } } ], "extra": [ 1, 248, 44, 16, 155, 178, 194, 165, 94, 229, 232, 212, 218, 239, 62, 106, 208, 213, 105, 119, 57, 107, 208, 240, 199, 206, 139, 12, 236, 49, 250, 160, 1, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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