← previous blocknext block →recent activity
Analyzing
Block #90,890,527
33 transactions · 30 stateful · 2026-07-27 22:26:19 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,890,527 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w39w414w516w017w118w219w321w427w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x6925548b…81cb
0x34b655…2a6f
4 touches
1 conflict
0x6925548b…81cc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity