← previous blocknext block →recent activity
Analyzing
Block #90,485,414
10 transactions · 8 stateful · 2026-07-26 12:28:14 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,485,414 · 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
1w02w13w04w15w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x932718b3…e12e
0x34b655…2a6f
4 touches
1 conflict
0xaaf64335…dcf1
0x34b655…2a6f
4 touches
1 conflict
0xc482682b…5a12
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x53edbc04…ae28
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
1 conflict on slot 0x932718b362…f9e12e
Audit this contract →
← previous block·next block →recent activity