← previous blocknext block →recent activity
Analyzing
Block #90,849,459
13 transactions · 13 stateful · 2026-07-27 18:59:41 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,849,459 · 13 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
2w03w16w07w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd61111…5bbc
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe4e9d128…437d
0x34b655…2a6f
4 touches
1 conflict
0xff68510a…09f1
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x3beed133…720d
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
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
3 conflicts on slot 0x2fd61111d8…455bbc
Audit this contract →
← previous block·next block →recent activity