← previous blocknext block →recent activity
Analyzing
Block #91,110,200
19 transactions · 17 stateful · 2026-07-28 16:52:21 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,110,200 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w212w313w414w015w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x36abaf69…6c7c
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x37d2d224…b565
0x34b655…2a6f
4 touches
1 conflict
0x469a005e…858c
0x34b655…2a6f
4 touches
1 conflict
0x469a005e…858d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
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
1 conflict on slot 0x07d8b1e8f0…0978c6
Audit this contract →
← previous block·next block →recent activity