← previous blocknext block →recent activity
Analyzing
Block #91,099,937
22 transactions · 20 stateful · 2026-07-28 16:00:43 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,099,937 · 22 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
2w03w17w08w09w210w112w313w116w217w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd1ebe246…d3dc
0x065c9d…c394
5 touches
3 conflicts
0xb356571d…539a
0x065c9d…c394
5 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x5bc6b706…fce6
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 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity