← previous blocknext block →recent activity
Analyzing
Block #90,618,193
18 transactions · 17 stateful · 2026-07-26 23:36:09 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,618,193 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w19w210w312w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0xde9d38a8…4c0f
0x34b655…2a6f
8 touches
6 conflicts
0x7032dc14…49ea
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x9440e1aa…1b94
0x34b655…2a6f
4 touches
1 conflict
0xa679a3e1…263c
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity