← previous blocknext block →recent activity
Analyzing
Block #89,700,253
16 transactions · 15 stateful · 2026-07-23 18:15:32 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,700,253 · 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
3w06w07w18w09w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0x8e4febf2…9e4f
0x370e2e…63b4
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x3cafb229…294b
0x0a2fbf…29b1
4 touches
1 conflict
0x3cafb229…294c
0x0a2fbf…29b1
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 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity