← previous blocknext block →recent activity
Analyzing
Block #90,774,594
13 transactions · 11 stateful · 2026-07-27 12:42:56 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,774,594 · 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
2w05w17w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6c3f6bf…7fac
0x34b655…2a6f
4 touches
1 conflict
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x576801fc…f80b
0x34b655…2a6f
3 touches
1 conflict
0x18e37e7d…bab2
0x34b655…2a6f
2 touches
0 conflicts
0x2f702750…347d
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 0xa6c3f6bf70…dc7fac
Audit this contract →
← previous block·next block →recent activity