← previous blocknext block →recent activity
Analyzing
Block #91,433,217
18 transactions · 17 stateful · 2026-07-29 19:59:38 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,433,217 · 18 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
1w02w14w05w16w27w09w310w411w413w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x08a39015…efa0
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x2f8c826e…c115
0x34b655…2a6f
4 touches
1 conflict
0x47729858…a47c
0x34b655…2a6f
4 touches
1 conflict
0x5dd62603…c6ac
0x34b655…2a6f
4 touches
1 conflict
0x626ee1b4…0b80
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity