← previous blocknext block →recent activity
Analyzing
Block #89,758,674
16 transactions · 15 stateful · 2026-07-23 23:10:29 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,758,674 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd50cd216…0d36
0x34b655…2a6f
6 touches
3 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
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
3 conflicts on slot 0xd50cd216e0…1d0d36
Audit this contract →
← previous block·next block →recent activity