← previous blocknext block →recent activity
Analyzing
Block #89,734,657
13 transactions · 12 stateful · 2026-07-23 21:09:09 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,734,657 · 13 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
3w04w16w27w38w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff29a21a…0d53
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6799eba…78e7
0x34b655…2a6f
4 touches
1 conflict
0xfe65bb7b…12d7
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0f82dba2…24d6
0x34b655…2a6f
4 touches
1 conflict
0x15eb6170…3da3
0x34b655…2a6f
4 touches
1 conflict
0x207e9f25…4724
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 0xff29a21ae7…940d53
Audit this contract →
← previous block·next block →recent activity