← previous blocknext block →recent activity
Analyzing
Block #83,199,237
13 transactions · 10 stateful · 2026-06-23 15:50:02 UTC
Parallelism
54/100
Blocked
60%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,199,237 · 13 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
1w04w16w07w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0x75f928fc…0465
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
6 touches
3 conflicts
0x7500c6c7…6b90
0x34b655…2a6f
6 touches
3 conflicts
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x4001a568…d51c
0x34b655…2a6f
4 touches
1 conflict
0x67a0f456…07e7
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity