← previous blocknext block →recent activity
Analyzing
Block #91,387,098
10 transactions · 9 stateful · 2026-07-29 16:06:22 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,387,098 · 10 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
1w02w14w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1febc2d0…0136
0x34b655…2a6f
2 touches
0 conflicts
0x2feefe4a…25c7
0x34b655…2a6f
2 touches
0 conflicts
0x34904ec4…aa8b
0x34b655…2a6f
2 touches
0 conflicts
0x445eb3ef…77f9
0x34b655…2a6f
2 touches
0 conflicts
0x494850d4…ecee
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity