Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 277b06c52fae9fc4fdc3ddd6365dd391efb8e59e85e5339806db0565d0174d23

Tx prefix hash: 887c1059a8eb6aa15ceafc61abba9e4072596cd1198fc0bc90b56bcc998936f2
Tx public key: 076aa98aef7b659374d3b3266656dd6271f449705d2e25d73bb81af6b47ef213
Timestamp: 1660166623 Timestamp [UCT]: 2022-08-10 21:23:43 Age [y:d:h:m:s]: 02:309:15:05:05
Block: 563062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742466 RingCT/type: yes/0
Extra: 01076aa98aef7b659374d3b3266656dd6271f449705d2e25d73bb81af6b47ef213021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.362612418000 dcy

stealth address amount amount idx
00: e16c3b9e46a47129bae5e2794541ac4bfbb15eb2aa2c8e5a0c57c74cb191c074 8.362612418000 995814 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": 563072, "vin": [ { "gen": { "height": 563062 } } ], "vout": [ { "amount": 8362612418, "target": { "key": "e16c3b9e46a47129bae5e2794541ac4bfbb15eb2aa2c8e5a0c57c74cb191c074" } } ], "extra": [ 1, 7, 106, 169, 138, 239, 123, 101, 147, 116, 211, 179, 38, 102, 86, 221, 98, 113, 244, 73, 112, 93, 46, 37, 215, 59, 184, 26, 246, 180, 126, 242, 19, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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