← previous blocknext block →recent activity
Analyzing
Block #90,234,563
12 transactions · 11 stateful · 2026-07-25 15:11:23 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,234,563 · 12 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb2dea2a…4925
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
4 touches
1 conflict
0x9538ea90…0536
0x34b655…2a6f
4 touches
1 conflict
0x1c188e80…18ce
0x34b655…2a6f
2 touches
0 conflicts
0x1d2cb39c…2322
0x34b655…2a6f
2 touches
0 conflicts
0xa1571d54…ae41
0x34b655…2a6f
2 touches
0 conflicts
0x2f1a69fa…c2ca
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 0xbb2dea2a57…464925
Audit this contract →
← previous block·next block →recent activity