← previous blocknext block →recent activity
Analyzing
Block #83,641,366
22 transactions · 18 stateful · 2026-06-25 17:02:17 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,641,366 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w110w011w112w213w314w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b1df992…40eb
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
10 touches
10 conflicts
0x82ff2023…1249
0x34b655…2a6f
10 touches
10 conflicts
0x7e6c970a…65af
0x34b655…2a6f
10 touches
10 conflicts
0x8ae827f1…aa36
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0x1b1df992d7…8240eb
Audit this contract →
← previous block·next block →recent activity