← previous blocknext block →recent activity
Analyzing
Block #90,036,336
15 transactions · 13 stateful · 2026-07-24 22:29:17 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,036,336 · 15 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
2w04w15w28w29w310w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c623175…29e4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x98acada1…77ed
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1f6b228e…f0a0
0x34b655…2a6f
4 touches
1 conflict
0x18fe7fdc…77f7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x4c62317513…a629e4
Audit this contract →
← previous block·next block →recent activity