← previous blocknext block →recent activity
Analyzing
Block #90,557,876
6 transactions · 6 stateful · 2026-07-26 18:32:43 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,557,876 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x746b3fc2…0b34
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4f3e95b9…b200
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x06c2c8c1…c2a8
0x34b655…2a6f
2 touches
0 conflicts
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x114d215a…a0c1
0x34b655…2a6f
2 touches
0 conflicts
0x2e6c7be1…d3e9
0x34b655…2a6f
2 touches
0 conflicts
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 0x746b3fc23f…8f0b34
Audit this contract →
← previous block·next block →recent activity