← previous blocknext block →recent activity
Analyzing
Block #90,221,934
12 transactions · 11 stateful · 2026-07-25 14:07:42 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,221,934 · 12 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
2w03w14w26w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x683dbabb…acd8
0x34b655…2a6f
6 touches
3 conflicts
0xd2b44b36…b48d
0x34b655…2a6f
4 touches
1 conflict
0xe7aba1c7…1141
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cb89fd4…9bb8
0x34b655…2a6f
4 touches
1 conflict
0xb683a2c9…b907
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
3 conflicts on slot 0x683dbabb7f…33acd8
Audit this contract →
← previous block·next block →recent activity