← previous blocknext block →recent activity
Analyzing
Block #90,042,325
16 transactions · 15 stateful · 2026-07-24 22:59:30 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,042,325 · 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
1w02w13w24w312w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xc7277122…8339
0x34b655…2a6f
4 touches
1 conflict
0xc7c09b47…3e3c
0x34b655…2a6f
4 touches
1 conflict
0x3727225e…a3cf
0x34b655…2a6f
3 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity