← previous blocknext block →recent activity
Analyzing
Block #90,210,959
14 transactions · 14 stateful · 2026-07-25 13:12:22 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,210,959 · 14 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
2w03w15w06w17w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaea2f389…0305
0x34b655…2a6f
6 touches
3 conflicts
0xd3571c75…1ad6
0x34b655…2a6f
4 touches
1 conflict
0xd83879b2…0bfb
0x34b655…2a6f
4 touches
1 conflict
0x1aa37a36…1d18
0x34b655…2a6f
4 touches
1 conflict
0x6f31d23e…8018
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
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 0xaea2f38908…f80305
Audit this contract →
← previous block·next block →recent activity