← previous blocknext block →recent activity
Analyzing
Block #90,243,024
13 transactions · 11 stateful · 2026-07-25 15:54:01 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,243,024 · 13 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
4w05w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x1c018ff8…69f3
0x34b655…2a6f
2 touches
0 conflicts
0x1ebb35bb…ef2a
0x34b655…2a6f
2 touches
0 conflicts
0x236375e3…00bd
0x34b655…2a6f
2 touches
0 conflicts
0x7561f24a…4522
0x34b655…2a6f
2 touches
0 conflicts
0x8e852ae9…fc5d
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
3 conflicts on slot 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity