← previous blocknext block →recent activity
Analyzing
Block #90,991,058
10 transactions · 10 stateful · 2026-07-28 06:52:06 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,991,058 · 10 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
2w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0xfcfb570f…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x623fd48c…9d77
0x34b655…2a6f
4 touches
1 conflict
0xb8806526…e31f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x6d524b12…2df3
0x34b655…2a6f
3 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 0x2029b74ed0…e1c206
Audit this contract →
← previous block·next block →recent activity