Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8756a248c673cef8f262636ae1c8521dd1579e3d4502ef0a25ea3022cc52da38

Tx prefix hash: 25df23546f800fd69a24e13898fc0dcbdf46c965cefac93c2567483033d6b819
Tx public key: 628893e8eaba6e983c2dda77d211ace3a513c0e2509f888b2d86615ae7ffec03
Timestamp: 1696804916 Timestamp [UCT]: 2023-10-08 22:41:56 Age [y:d:h:m:s]: 01:183:23:58:08
Block: 865463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392538 RingCT/type: yes/0
Extra: 01628893e8eaba6e983c2dda77d211ace3a513c0e2509f888b2d86615ae7ffec030211000000024b8f5122000000000000000000

1 output(s) for total of 0.832457066000 dcy

stealth address amount amount idx
00: c77b2ced1bf979a4c67a7dff015396c0e1ad563665b7473898d08f65673c23e3 0.832457066000 1319999 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": 865473, "vin": [ { "gen": { "height": 865463 } } ], "vout": [ { "amount": 832457066, "target": { "key": "c77b2ced1bf979a4c67a7dff015396c0e1ad563665b7473898d08f65673c23e3" } } ], "extra": [ 1, 98, 136, 147, 232, 234, 186, 110, 152, 60, 45, 218, 119, 210, 17, 172, 227, 165, 19, 192, 226, 80, 159, 136, 139, 45, 134, 97, 90, 231, 255, 236, 3, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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