← previous blocknext block →recent activity
Analyzing
Block #90,208,492
8 transactions · 8 stateful · 2026-07-25 12:59:57 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,208,492 · 8 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
1w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4216a5a9…7428
0x34b655…2a6f
2 touches
0 conflicts
0x487aa334…7ef2
0x34b655…2a6f
2 touches
0 conflicts
0x4c6387c5…575a
0x34b655…2a6f
2 touches
0 conflicts
0x5484fc7f…a8d8
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 0x749a4cb261…2c15f8
Audit this contract →
← previous block·next block →recent activity