← previous blocknext block →recent activity
Analyzing
Block #91,001,341
9 transactions · 9 stateful · 2026-07-28 07:44:15 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,001,341 · 9 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
2w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc208ef3c…aa4b
0x34b655…2a6f
4 touches
1 conflict
0xf28a9fc2…05e4
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
0x2b46c0…1669
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 0xc208ef3cc7…80aa4b
Audit this contract →
← previous block·next block →recent activity