← previous blocknext block →recent activity
Analyzing
Block #90,866,933
9 transactions · 9 stateful · 2026-07-27 20:27:38 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,866,933 · 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
1w02w13w24w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ae4a85e…c097
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe33a222b…710f
0x34b655…2a6f
4 touches
1 conflict
0x17df9a7e…0018
0x34b655…2a6f
2 touches
0 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
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
3 conflicts on slot 0x6ae4a85e7c…0fc097
Audit this contract →
← previous block·next block →recent activity