← previous blocknext block →recent activity
Analyzing
Block #89,860,784
7 transactions · 6 stateful · 2026-07-24 07:45:36 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,860,784 · 7 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16ca426f…8382
0x34b655…2a6f
6 touches
3 conflicts
0x6da69409…e75d
0x34b655…2a6f
6 touches
3 conflicts
0xc516fef7…841c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xacfd8774…87ec
0x34b655…2a6f
4 touches
1 conflict
0xec0af936…5c04
0x34b655…2a6f
4 touches
1 conflict
0x363f99e4…32c8
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
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
3 conflicts on slot 0x16ca426f52…6b8382
Audit this contract →
← previous block·next block →recent activity