← previous blocknext block →recent activity
Analyzing
Block #90,723,020
10 transactions · 10 stateful · 2026-07-27 08:23:30 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,723,020 · 10 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
2w03w14w25w36w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8c37753…43a6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4984f7be…d515
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0xff107718…55e9
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d4
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0xe70bdeae…f1ee
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
6 conflicts on slot 0xd8c37753b0…7443a6
Audit this contract →
← previous block·next block →recent activity