← previous blocknext block →recent activity
Analyzing
Block #83,631,937
25 transactions · 20 stateful · 2026-06-25 15:59:17 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,631,937 · 25 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
1w05w06w110w011w112w213w320w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x610aa855…5ecd
0x34b655…2a6f
6 touches
3 conflicts
0x0ac7b0a9…5c36
0x34b655…2a6f
4 touches
1 conflict
0x1a1ff3c7…bc09
0x34b655…2a6f
4 touches
1 conflict
0x5396d712…a139
0x34b655…2a6f
4 touches
1 conflict
0x6767aeb1…eabc
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity