← previous blocknext block →recent activity
Analyzing
Block #90,513,261
10 transactions · 9 stateful · 2026-07-26 14:48:18 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,513,261 · 10 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
2w03w14w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x299c0f04…09cf
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x2bb831e8…ae55
0x34b655…2a6f
6 touches
3 conflicts
0xffc26b06…715e
0x34b655…2a6f
6 touches
3 conflicts
0xffc26b06…715f
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0aa42ae9…ed69
0x34b655…2a6f
4 touches
1 conflict
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 0x299c0f043b…7d09cf
Audit this contract →
← previous block·next block →recent activity