← previous blocknext block →recent activity
Analyzing
Block #89,752,181
14 transactions · 13 stateful · 2026-07-23 22:37:44 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,752,181 · 14 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
4w06w17w28w09w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76196ad0…ce0c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x055b5b38…8737
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x2fdfe038…c16c
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
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
6 conflicts on slot 0x76196ad0db…ffce0c
Audit this contract →
← previous block·next block →recent activity