← previous blocknext block →recent activity
Analyzing
Block #91,892,175
19 transactions · 17 stateful · 2026-07-31 10:28:35 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,892,175 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w18w110w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xb852cf41…12b6
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x40f4633f…2138
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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
1 conflict on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity