← previous blocknext block →recent activity
Analyzing
Block #90,450,079
5 transactions · 5 stateful · 2026-07-26 09:30:26 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,450,079 · 5 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
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xe71e3c49…e75d
0x34b655…2a6f
4 touches
1 conflict
0x0ab1986a…4790
0x34b655…2a6f
4 touches
1 conflict
0x2c8f52ce…fe9a
0x34b655…2a6f
2 touches
0 conflicts
0x2ef451c7…edf8
0x34b655…2a6f
2 touches
0 conflicts
0x5690767c…9028
0x34b655…2a6f
2 touches
0 conflicts
0x6cc79ec6…3edb
0x34b655…2a6f
2 touches
0 conflicts
0x72c8aeb2…9921
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity