← previous blocknext block →recent activity
Analyzing
Block #90,789,123
16 transactions · 14 stateful · 2026-07-27 13:56:04 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,789,123 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b5fdd23…afe5
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e37574f…4145
0x34b655…2a6f
4 touches
1 conflict
0x638e8625…08dc
0x34b655…2a6f
4 touches
1 conflict
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0x65c50a7f…f491
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0x8b5fdd2315…31afe5
Audit this contract →
← previous block·next block →recent activity