← previous blocknext block →recent activity
Analyzing
Block #91,130,858
15 transactions · 14 stateful · 2026-07-28 18:36:15 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,130,858 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w310w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf4ff6e8d…0427
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x3c0d2f30…1afb
0x34b655…2a6f
4 touches
1 conflict
0x5c1848ef…f700
0x34b655…2a6f
4 touches
1 conflict
0x786cd4f6…f045
0x34b655…2a6f
4 touches
1 conflict
0x87a28e89…6b3e
0x34b655…2a6f
4 touches
1 conflict
0x9a54f439…de63
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity