← previous blocknext block →recent activity
Analyzing
Block #89,702,386
12 transactions · 9 stateful · 2026-07-23 18:26:16 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,702,386 · 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
4w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x315e07b8…9823
0x34b655…2a6f
2 touches
0 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
2 touches
0 conflicts
0x438268c2…c848
0x34b655…2a6f
2 touches
0 conflicts
0x438268c2…c849
0x34b655…2a6f
2 touches
0 conflicts
0x60b8bcf1…fb76
0x34b655…2a6f
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 0xa80684c9ae…1b3948
Audit this contract →
← previous block·next block →recent activity