← previous blocknext block →recent activity
Analyzing
Block #91,128,834
16 transactions · 16 stateful · 2026-07-28 18:26:05 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,128,834 · 16 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
4w05w16w27w310w011w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0xd31913b6…6e9a
0x754704…b603
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity