← previous blocknext block →recent activity
Analyzing
Block #90,286,650
9 transactions · 8 stateful · 2026-07-25 19:34:27 UTC
Parallelism
44/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,286,650 · 9 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
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5aa39a…20b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3ac99a6c…0433
0x34b655…2a6f
4 touches
1 conflict
0x3f54073d…780a
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x4af8f8d2…0850
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 0x6d5aa39ab9…1720b8
Audit this contract →
← previous block·next block →recent activity