← previous blocknext block →recent activity
Analyzing
Block #90,124,682
10 transactions · 9 stateful · 2026-07-25 05:57:34 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,124,682 · 10 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
1w02w13w04w15w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0x9a3ccb93…8161
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0x0181bb3798…ed6628
Audit this contract →
← previous block·next block →recent activity