← previous blocknext block →recent activity
Analyzing
Block #90,537,600
10 transactions · 9 stateful · 2026-07-26 16:50:43 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,537,600 · 10 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
2w03w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x02c03ee2…3de5
0x34b655…2a6f
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x10797f0b…439a
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 0xd93edb3f20…0394ec
Audit this contract →
← previous block·next block →recent activity