← previous blocknext block →recent activity
Analyzing
Block #83,636,504
20 transactions · 18 stateful · 2026-06-25 16:29:49 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,636,504 · 20 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
1w02w14w05w16w27w38w49w515w016w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x1b429191…8b0d
0x34b655…2a6f
8 touches
6 conflicts
0x1bcbf4c9…d744
0x34b655…2a6f
8 touches
6 conflicts
0x20ed6f44…2fb1
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x39af5a1b…b4bd
0x34b655…2a6f
8 touches
6 conflicts
0x505f101e…7ad6
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity