← previous blocknext block →recent activity
Analyzing
Block #90,630,406
17 transactions · 16 stateful · 2026-07-27 00:37:36 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,630,406 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w18w29w310w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53699236…fede
0x34b655…2a6f
8 touches
6 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x6284960e…adc8
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x53699236c4…57fede
Audit this contract →
← previous block·next block →recent activity