← previous blocknext block →recent activity
Analyzing
Block #91,008,314
12 transactions · 9 stateful · 2026-07-28 08:19:32 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,008,314 · 12 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x672c8097…c166
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x3270f906…a0e9
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 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity