← previous blocknext block →recent activity
Analyzing
Block #89,676,953
22 transactions · 18 stateful · 2026-07-23 16:18:00 UTC
Parallelism
82/100
Blocked
28%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,676,953 · 22 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
3w04w15w06w17w28w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf7963b5…5eef
0x34b655…2a6f
4 touches
1 conflict
0xdfc01d93…9d93
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0d55d89d…a4ec
0x34b655…2a6f
4 touches
1 conflict
0x25d52624…f992
0x34b655…2a6f
4 touches
1 conflict
0x2e286baf…5b8d
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 0xf0d45ffdb0…4089cf
Audit this contract →
← previous block·next block →recent activity