← previous blocknext block →recent activity
Analyzing
Block #90,852,112
22 transactions · 22 stateful · 2026-07-27 19:13:01 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,852,112 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w28w09w110w311w413w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28d74e20…c54e
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92d4e9d1…b273
0x34b655…2a6f
6 touches
3 conflicts
0xceb7aa9e…2453
0x34b655…2a6f
6 touches
3 conflicts
0xf3383813…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0xa80684c9…3948
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
10 conflicts on slot 0x28d74e2060…4ac54e
Audit this contract →
← previous block·next block →recent activity