← previous blocknext block →recent activity
Analyzing
Block #89,749,457
16 transactions · 12 stateful · 2026-07-23 22:23:59 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,749,457 · 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
7w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30685372…8f8d
0x34b655…2a6f
4 touches
1 conflict
0x99b77a72…37e4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x29856edf…841b
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da89
0x34b655…2a6f
4 touches
1 conflict
0xb5fd2f20…30c7
0x34b655…2a6f
3 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 0x306853721a…968f8d
Audit this contract →
← previous block·next block →recent activity