← previous blocknext block →recent activity
Analyzing
Block #89,742,419
12 transactions · 12 stateful · 2026-07-23 21:48:24 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,742,419 · 12 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0xa92dbaef…810e
0x34b655…2a6f
4 touches
1 conflict
0xc64c7dc8…8c62
0x34b655…2a6f
4 touches
1 conflict
0xc64c7dc8…8c63
0x34b655…2a6f
4 touches
1 conflict
0xdcb63584…bae4
0x34b655…2a6f
4 touches
1 conflict
0xc54b98c6…e95d
0x34b655…2a6f
3 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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 0x5666db7d94…495dc4
Audit this contract →
← previous block·next block →recent activity