Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de77c7c1b804f8c849ecde23844078963db47b4bc0b971cc00b235b072283e91

Tx prefix hash: 05b7d86d6ff26fe74583afbf2a9a14dcd6aa1dc51fe38bbd449ee9ec642d4de6
Tx public key: 1c8286193205e6af5ed00d7835a7519c8113980d1e3f081de9e1ea2561affc2e
Timestamp: 1577392648 Timestamp [UCT]: 2019-12-26 20:37:28 Age [y:d:h:m:s]: 04:339:12:40:54
Block: 32440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131731 RingCT/type: yes/0
Extra: 011c8286193205e6af5ed00d7835a7519c8113980d1e3f081de9e1ea2561affc2e021100000008d81c26c0000000000000000000

1 output(s) for total of 479.196538479000 dcy

stealth address amount amount idx
00: fb7b5712edfdb602ca24c119b4edffdf57868a924b0115277914002ed55e2cfa 479.196538479000 53947 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": 32450, "vin": [ { "gen": { "height": 32440 } } ], "vout": [ { "amount": 479196538479, "target": { "key": "fb7b5712edfdb602ca24c119b4edffdf57868a924b0115277914002ed55e2cfa" } } ], "extra": [ 1, 28, 130, 134, 25, 50, 5, 230, 175, 94, 208, 13, 120, 53, 167, 81, 156, 129, 19, 152, 13, 30, 63, 8, 29, 233, 225, 234, 37, 97, 175, 252, 46, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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