← previous blocknext block →recent activity
Analyzing
Block #89,858,365
14 transactions · 14 stateful · 2026-07-24 07:33:26 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,858,365 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w38w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x2da3a8ad…628d
0x34b655…2a6f
4 touches
1 conflict
0x2da3a8ad…628e
0x34b655…2a6f
4 touches
1 conflict
0x30c0f89e…b0db
0x34b655…2a6f
4 touches
1 conflict
0x4b6e6a9d…3dc1
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73f
0x34b655…2a6f
4 touches
1 conflict
0x6d66043a…fa18
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 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity