← previous blocknext block →recent activity
Analyzing
Block #90,212,533
9 transactions · 8 stateful · 2026-07-25 13:20:17 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,212,533 · 9 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x0a1643e3…e20d
0x34b655…2a6f
2 touches
0 conflicts
0x16e51d18…5d99
0x34b655…2a6f
2 touches
0 conflicts
0x19ca6d94…05f5
0x34b655…2a6f
2 touches
0 conflicts
0x1d875519…50f9
0x34b655…2a6f
2 touches
0 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
2 touches
0 conflicts
0x3170337f…16e1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity