← previous blocknext block →recent activity
Analyzing
Block #90,718,318
16 transactions · 15 stateful · 2026-07-27 07:59:50 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,718,318 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w19w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf22814…27c8
0x34b655…2a6f
4 touches
1 conflict
0xfb24441a…4183
0x34b655…2a6f
4 touches
1 conflict
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0xfaf2281433…4927c8
Audit this contract →
← previous block·next block →recent activity