← previous blocknext block →recent activity
Analyzing
Block #89,585,841
14 transactions · 12 stateful · 2026-07-23 06:41:33 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,585,841 · 14 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
1w03w14w05w18w09w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x28c714d9…9438
0xa6afd3…d132
4 touches
1 conflict
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity