← previous blocknext block →recent activity
Analyzing
Block #90,454,781
9 transactions · 8 stateful · 2026-07-26 09:54:05 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,454,781 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2ffa1f3…d3ae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x7634a3f4…7f24
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
6 conflicts on slot 0xd2ffa1f3c7…48d3ae
Audit this contract →
← previous block·next block →recent activity