← previous blocknext block →recent activity
Analyzing
Block #90,917,398
12 transactions · 12 stateful · 2026-07-28 00:41:30 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,917,398 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w39w411w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0x32ffd4e4…5fdd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f0f32bc…a96f
0x34b655…2a6f
4 touches
1 conflict
0x5156d4d5…148a
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
3 conflicts on slot 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity