← previous blocknext block →recent activity
Analyzing
Block #90,772,089
12 transactions · 11 stateful · 2026-07-27 12:30:20 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,772,089 · 12 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
1w02w05w16w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0x697e6f54…588f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x8b7af792…9ef0
0x34b655…2a6f
4 touches
1 conflict
0x8ebf5869…6785
0x34b655…2a6f
4 touches
1 conflict
0xec152baf…a069
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
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 0x6396a4c45b…5cf626
Audit this contract →
← previous block·next block →recent activity