← previous blocknext block →recent activity
Analyzing
Block #83,570,568
12 transactions · 11 stateful · 2026-06-25 09:09:33 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,570,568 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w09w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
6 touches
3 conflicts
0xde08018b…f3be
0x34b655…2a6f
6 touches
3 conflicts
0x4af01092…a099
0x34b655…2a6f
4 touches
1 conflict
0x571cb36d…3b3d
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity