← previous blocknext block →recent activity
Analyzing
Block #91,406,697
18 transactions · 18 stateful · 2026-07-29 17:45:08 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,406,697 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w49w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x1ee7ce60…8220
0x34b655…2a6f
6 touches
3 conflicts
0x5cc0e9c8…3ae6
0x34b655…2a6f
6 touches
3 conflicts
0x803cd43b…b348
0x34b655…2a6f
6 touches
3 conflicts
0xb5b879be…8943
0x34b655…2a6f
6 touches
3 conflicts
0xd9461b7e…31bc
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity