← previous blocknext block →recent activity
Analyzing
Block #90,642,915
12 transactions · 10 stateful · 2026-07-27 01:40:31 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,642,915 · 12 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
2w03w14w07w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f68ff96…38a6
0x34b655…2a6f
6 touches
3 conflicts
0x3e30f1bf…6453
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
0x34b655…2a6f
4 touches
1 conflict
0x6625830a…8521
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x2f68ff96e7…b538a6
Audit this contract →
← previous block·next block →recent activity