← previous blocknext block →recent activity
Analyzing
Block #90,459,052
7 transactions · 6 stateful · 2026-07-26 10:15:34 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,459,052 · 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
1w02w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xacb6de83…d893
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x42f6865c…209e
0x34b655…2a6f
2 touches
0 conflicts
0x588c5b6a…60d2
0x34b655…2a6f
2 touches
0 conflicts
0x6100f5dd…6a7f
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 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity