← previous blocknext block →recent activity
Analyzing
Block #89,735,731
19 transactions · 16 stateful · 2026-07-23 21:14:35 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,735,731 · 19 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
6w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x207e9f25…4724
0x34b655…2a6f
4 touches
1 conflict
0x207e9f25…4725
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5edb8bbe…bc75
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x818b0b44…ff6f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x207e9f2578…544724
Audit this contract →
← previous block·next block →recent activity