Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ee073ee0619316f14246da0819dba6920261ec04c85083b954fb8d164a61eb

Tx prefix hash: 73e0ded63138cc62e937df087053250f07bbc1a0b77ec1da58c3a13e06ae2fc7
Tx public key: 1b28f34bfeb5c26a35f1ed07c9dffac94dc26dfff59473f114320ce6f328ad6e
Timestamp: 1699483301 Timestamp [UCT]: 2023-11-08 22:41:41 Age [y:d:h:m:s]: 01:153:04:36:52
Block: 887466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370680 RingCT/type: yes/0
Extra: 011b28f34bfeb5c26a35f1ed07c9dffac94dc26dfff59473f114320ce6f328ad6e021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.703812116000 dcy

stealth address amount amount idx
00: 053b36ad94726787ae236b2d1ac4836358d44b4a665864e87f393b7383038c1b 0.703812116000 1343351 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": 887476, "vin": [ { "gen": { "height": 887466 } } ], "vout": [ { "amount": 703812116, "target": { "key": "053b36ad94726787ae236b2d1ac4836358d44b4a665864e87f393b7383038c1b" } } ], "extra": [ 1, 27, 40, 243, 75, 254, 181, 194, 106, 53, 241, 237, 7, 201, 223, 250, 201, 77, 194, 109, 255, 245, 148, 115, 241, 20, 50, 12, 230, 243, 40, 173, 110, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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