← previous blocknext block →recent activity
Analyzing
Block #90,629,052
10 transactions · 10 stateful · 2026-07-27 00:30:47 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,629,052 · 10 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
1w03w15w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64dfceb0…c5d7
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e2
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e3
0x34b655…2a6f
2 touches
0 conflicts
0x330357df…91cb
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 0x64dfceb059…5ac5d7
Audit this contract →
← previous block·next block →recent activity