← previous blocknext block →recent activity
Analyzing
Block #90,978,613
11 transactions · 10 stateful · 2026-07-28 05:49:25 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,978,613 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x4c61dc6b…c12a
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x935e0525…f741
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 0x6713b0185b…1305f3
Audit this contract →
← previous block·next block →recent activity