← previous blocknext block →recent activity
Analyzing
Block #91,985,113
18 transactions · 16 stateful · 2026-07-31 18:16:03 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,985,113 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w110w213w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf67e423…5703
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0xa1d97a96…6fa7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd70ab6b5…64cd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0xdf67e4238e…4c5703
Audit this contract →
← previous block·next block →recent activity