← previous blocknext block →recent activity
Analyzing
Block #91,404,186
9 transactions · 8 stateful · 2026-07-29 17:32:25 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,404,186 · 9 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x8c5c7e52…01b8
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x0802d0d8…dd0c
0x34b655…2a6f
2 touches
0 conflicts
0x246ec521…cc7c
0x34b655…2a6f
2 touches
0 conflicts
0x2b747f7d…4d32
0x34b655…2a6f
2 touches
0 conflicts
0x37b45d78…f241
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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 0x1b5d2e607a…9999b5
Audit this contract →
← previous block·next block →recent activity