← previous blocknext block →recent activity
Analyzing
Block #91,440,339
22 transactions · 20 stateful · 2026-07-29 20:35:28 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,440,339 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w09w013w114w215w316w417w518w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0x2b070180…7ca7
0x34b655…2a6f
6 touches
3 conflicts
0x2d7b3d63…c856
0x34b655…2a6f
4 touches
1 conflict
0x689db929…2f26
0x34b655…2a6f
4 touches
1 conflict
0x6ba89834…1826
0x34b655…2a6f
4 touches
1 conflict
0x735f7df7…2f5b
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity