← previous blocknext block →recent activity
Analyzing
Block #90,699,701
10 transactions · 9 stateful · 2026-07-27 06:26:12 UTC
Parallelism
40/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,699,701 · 10 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
2w03w14w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65104f89…bbce
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0xbb162541…2f0c
0x34b655…2a6f
4 touches
1 conflict
0xf83f4309…2363
0x34b655…2a6f
4 touches
1 conflict
0x5f7bc3e4…aac1
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
10 conflicts on slot 0x65104f8913…a8bbce
Audit this contract →
← previous block·next block →recent activity