← previous blocknext block →recent activity
Analyzing
Block #89,750,663
14 transactions · 12 stateful · 2026-07-23 22:30:04 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,750,663 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe20cb8f…f03d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xed91ba52…5bde
0x34b655…2a6f
4 touches
1 conflict
0x00893bb8…77ee
0x34b655…2a6f
4 touches
1 conflict
0x0de29f47…1c06
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x3cd05e42…f9b5
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 0xfe20cb8f2c…3ef03d
Audit this contract →
← previous block·next block →recent activity