← previous blocknext block →recent activity
Analyzing
Block #90,688,903
10 transactions · 10 stateful · 2026-07-27 05:31:53 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,688,903 · 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
2w03w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0xab9ed6fb…5c25
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x1ad1cef6…0e60
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4065
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3c9bce0e…0440
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 0x8329c51ebc…7a4064
Audit this contract →
← previous block·next block →recent activity