← previous blocknext block →recent activity
Analyzing
Block #89,514,852
23 transactions · 21 stateful · 2026-07-22 22:47:25 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,514,852 · 23 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
1w03w14w07w08w112w114w215w016w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0a2ca0ad…6411
0x0a2fbf…29b1
4 touches
1 conflict
0x0a2ca0ad…6412
0x0a2fbf…29b1
4 touches
1 conflict
0x0a2ca0ad…6415
0x0a2fbf…29b1
4 touches
1 conflict
0x3f3fab8b…c9b5
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x6474161a…6a37
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity