← previous blocknext block →recent activity
Analyzing
Block #91,132,489
10 transactions · 10 stateful · 2026-07-28 18:44:28 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,132,489 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x169a7c68…3874
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe4c602c1…04be
0x34b655…2a6f
4 touches
1 conflict
0x589623ea…8ce2
0x34b655…2a6f
4 touches
1 conflict
0x501c4813…cca6
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcd
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 0x169a7c6813…633874
Audit this contract →
← previous block·next block →recent activity