← previous blocknext block →recent activity
Analyzing
Block #90,454,373
7 transactions · 6 stateful · 2026-07-26 09:52:02 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,454,373 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3513c01b…8491
0x34b655…2a6f
4 touches
1 conflict
0xd2ffa1f3…d3ae
0x34b655…2a6f
4 touches
1 conflict
0xf7d99172…f1e1
0x34b655…2a6f
4 touches
1 conflict
0xc3de326c…d0fc
0x34b655…2a6f
4 touches
1 conflict
0xc3de326c…d0fd
0x34b655…2a6f
4 touches
1 conflict
0xe8780119…3bfd
0x34b655…2a6f
3 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
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 0x3513c01bca…6d8491
Audit this contract →
← previous block·next block →recent activity