← previous blocknext block →recent activity
Analyzing
Block #91,002,090
11 transactions · 11 stateful · 2026-07-28 07:48:03 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,002,090 · 11 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
1w05w17w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd190722…ecae
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x48f735bf…e965
0x34b655…2a6f
4 touches
1 conflict
0x54d68470…4b32
0x34b655…2a6f
4 touches
1 conflict
0x20ff72d4…5971
0x34b655…2a6f
2 touches
0 conflicts
0xbdacb500…92f7
0x34b655…2a6f
2 touches
0 conflicts
0x2dd83168…8144
0x34b655…2a6f
2 touches
0 conflicts
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 0xdd190722b1…12ecae
Audit this contract →
← previous block·next block →recent activity