← previous blocknext block →recent activity
Analyzing
Block #89,702,245
17 transactions · 13 stateful · 2026-07-23 18:25:33 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,702,245 · 17 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
1w03w16w07w111w114w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xff393f19…4dd2
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0002
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity