← previous blocknext block →recent activity
Analyzing
Block #90,720,809
9 transactions · 9 stateful · 2026-07-27 08:12:23 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,720,809 · 9 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x007892de…5752
0x34b655…2a6f
4 touches
1 conflict
0x07a9a4ce…6b6d
0x34b655…2a6f
4 touches
1 conflict
0x07a9a4ce…6b6e
0x34b655…2a6f
4 touches
1 conflict
0x2ba15dc4…04d6
0x34b655…2a6f
4 touches
1 conflict
0x37279f6d…e4fb
0x34b655…2a6f
4 touches
1 conflict
0x41bd2e6b…e240
0x34b655…2a6f
4 touches
1 conflict
0x46e558af…7871
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
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
1 conflict on slot 0x007892de1e…635752
Audit this contract →
← previous block·next block →recent activity