← previous blocknext block →recent activity
Analyzing
Block #90,441,119
7 transactions · 7 stateful · 2026-07-26 08:45:05 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,441,119 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa10e928f…3b92
0x34b655…2a6f
4 touches
1 conflict
0x7cd78950…607c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x2acba407…43c8
0x34b655…2a6f
2 touches
0 conflicts
0x3560a56c…d95d
0x34b655…2a6f
2 touches
0 conflicts
0x38948e75…437a
0x34b655…2a6f
2 touches
0 conflicts
0x5af098c7…4806
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 0xa10e928f74…7c3b92
Audit this contract →
← previous block·next block →recent activity