← previous blocknext block →recent activity
Analyzing
Block #90,483,324
10 transactions · 9 stateful · 2026-07-26 12:17:44 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,483,324 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x075dcfb7…1c3b
0x34b655…2a6f
4 touches
1 conflict
0xdb9db9e5…fe69
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x682b0e45…f0bd
0x065c9d…c394
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb15c58ec…bd83
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 0x075dcfb7dc…741c3b
Audit this contract →
← previous block·next block →recent activity