← previous blocknext block →recent activity
Analyzing
Block #83,665,816
11 transactions · 8 stateful · 2026-06-25 19:45:20 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,665,816 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xf86f15cd…38af
0x34b655…2a6f
4 touches
1 conflict
0x12873296…ab4c
0x34b655…2a6f
4 touches
1 conflict
0x2405db7f…723e
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
2 touches
0 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity