← previous blocknext block →recent activity
Analyzing
Block #90,961,598
16 transactions · 16 stateful · 2026-07-28 04:23:49 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,961,598 · 16 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
2w03w15w06w07w18w29w010w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x966d72e7…a32e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x2db15f3e…289d
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…00c9
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
6 conflicts on slot 0x966d72e72f…62a32e
Audit this contract →
← previous block·next block →recent activity