← previous blocknext block →recent activity
Analyzing
Block #91,285,094
11 transactions · 10 stateful · 2026-07-29 07:33:01 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,285,094 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b98ece0…4dc6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd6289e73…4276
0x34b655…2a6f
6 touches
3 conflicts
0xd2e35622…f491
0x34b655…2a6f
6 touches
3 conflicts
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x03d53e11…3f6f
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
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
3 conflicts on slot 0x0b98ece071…d34dc6
Audit this contract →
← previous block·next block →recent activity