← previous blocknext block →recent activity
Analyzing
Block #89,836,502
13 transactions · 13 stateful · 2026-07-24 05:43:18 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,836,502 · 13 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
1w02w13w15w26w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd3bdfb…7537
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x28a10a99…2f36
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x553d09ad…e640
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 0x0dd3bdfbfd…197537
Audit this contract →
← previous block·next block →recent activity