← previous blocknext block →recent activity
Analyzing
Block #90,696,839
9 transactions · 9 stateful · 2026-07-27 06:11:48 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,696,839 · 9 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
2w03w14w26w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21ca661f…6b6a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x1ed218ce…0548
0x34b655…2a6f
4 touches
1 conflict
0xaad78968…ac39
0x065c9d…c394
2 touches
0 conflicts
0xc161c03d…7cb5
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0x21ca661fdd…6e6b6a
Audit this contract →
← previous block·next block →recent activity