← previous blocknext block →recent activity
Analyzing
Block #90,790,111
7 transactions · 7 stateful · 2026-07-27 14:01:02 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,790,111 · 7 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x007892de…5752
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x1622a56b…fb75
0x34b655…2a6f
2 touches
0 conflicts
0x1630d4a2…34a7
0x34b655…2a6f
2 touches
0 conflicts
0x2c5519b9…7384
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 0x007892de1e…635752
Audit this contract →
← previous block·next block →recent activity