← previous blocknext block →recent activity
Analyzing
Block #90,836,060
6 transactions · 6 stateful · 2026-07-27 17:52:17 UTC
Parallelism
33/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,836,060 · 6 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x9ddc4efa…8e27
0x34b655…2a6f
4 touches
1 conflict
0x5ea68b67…6097
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
3 conflicts on slot 0xfb31d278a3…299107
Audit this contract →
← previous block·next block →recent activity