← previous blocknext block →recent activity
Analyzing
Block #89,539,447
15 transactions · 14 stateful · 2026-07-23 01:31:38 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,539,447 · 15 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
6w07w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x050e3433…ecb3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6b76ce29…0e84
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfef0ce0a…aa80
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0xb37ed418…0a6d
0x34b655…2a6f
4 touches
1 conflict
0xc13e1d5c…62c7
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
6 conflicts on slot 0x050e343364…bbecb3
Audit this contract →
← previous block·next block →recent activity