← previous blocknext block →recent activity
Analyzing
Block #90,866,867
8 transactions · 7 stateful · 2026-07-27 20:27:18 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,866,867 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf64bd4ab…6d1a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1bb624f3…c1b3
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xe3280296…788e
0x34b655…2a6f
3 touches
1 conflict
0x0e52d81f…461e
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 0xf64bd4ab2e…416d1a
Audit this contract →
← previous block·next block →recent activity