← previous blocknext block →recent activity
Analyzing
Block #91,203,813
20 transactions · 20 stateful · 2026-07-29 00:43:15 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,203,813 · 20 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
1w02w13w24w05w16w27w38w311w413w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95dd1dda…bc0e
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
6 touches
3 conflicts
0x1cdf1b48…9f5e
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
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
6 conflicts on slot 0x95dd1ddad2…f7bc0e
Audit this contract →
← previous block·next block →recent activity