← previous blocknext block →recent activity
Analyzing
Block #90,622,938
16 transactions · 16 stateful · 2026-07-27 00:00:01 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,622,938 · 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
2w03w14w05w16w07w28w311w013w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 conflicts
0x0a005879…de60
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x2ba15dc4…04d6
0x34b655…2a6f
4 touches
1 conflict
0x3684bb9c…2e61
0x34b655…2a6f
4 touches
1 conflict
0x575dc174…842f
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
3 conflicts on slot 0x7032dc1485…0e49ea
Audit this contract →
← previous block·next block →recent activity