← previous blocknext block →recent activity
Analyzing
Block #90,446,634
16 transactions · 15 stateful · 2026-07-26 09:13:06 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,446,634 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5e6defa…7266
0x34b655…2a6f
4 touches
1 conflict
0xc3656cd1…8269
0x34b655…2a6f
4 touches
1 conflict
0xcbe863a2…b2dd
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x071ff290…ec09
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5ee667a1…2a60
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xb5e6defa5e…8f7266
Audit this contract →
← previous block·next block →recent activity