← previous blocknext block →recent activity
Analyzing
Block #91,040,529
15 transactions · 14 stateful · 2026-07-28 11:01:45 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,040,529 · 15 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
2w03w04w16w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x6cb2b931…f8a7
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf8ceaa24…6e8e
0x851145…3f07
4 touches
1 conflict
0x096c7f83…68af
0x34b655…2a6f
2 touches
0 conflicts
0x0ab4b967…cf48
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 0x6719a76784…b59d62
Audit this contract →
← previous block·next block →recent activity