← previous blocknext block →recent activity
Analyzing
Block #90,783,506
18 transactions · 17 stateful · 2026-07-27 13:27:46 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,783,506 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w27w311w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x025fef2f…9738
0x34b655…2a6f
4 touches
1 conflict
0x0efb348e…6809
0x34b655…2a6f
4 touches
1 conflict
0x114324a9…6d5e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3e30f1bf…6453
0x34b655…2a6f
4 touches
1 conflict
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0x7032dc14…49ea
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity