← previous blocknext block →recent activity
Analyzing
Block #90,323,325
18 transactions · 16 stateful · 2026-07-25 22:40:54 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,323,325 · 18 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
2w07w08w19w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e83dc2…b7a0
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1ca2c9cd…8f8e
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x60270642…c780
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x05e83dc20e…d3b7a0
Audit this contract →
← previous block·next block →recent activity