← previous blocknext block →recent activity
Analyzing
Block #91,279,043
7 transactions · 6 stateful · 2026-07-29 07:02:34 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,279,043 · 7 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebd735e5…ea5d
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
2 touches
0 conflicts
0x28c62bca…b746
0x34b655…2a6f
2 touches
0 conflicts
0x2d2723c7…da1c
0x34b655…2a6f
2 touches
0 conflicts
0x398c3a27…6f7e
0x34b655…2a6f
2 touches
0 conflicts
0x5e4b65e1…ebe1
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 0xebd735e588…dcea5d
Audit this contract →
← previous block·next block →recent activity