← previous blocknext block →recent activity
Analyzing
Block #89,699,108
14 transactions · 14 stateful · 2026-07-23 18:09:47 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,699,108 · 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
2w03w18w09w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc80409b7…072a
0x34b655…2a6f
4 touches
1 conflict
0xc92ea287…c4df
0x34b655…2a6f
4 touches
1 conflict
0x20d33f08…5249
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x217a44a9…a7a9
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4376
0x34b655…2a6f
2 touches
0 conflicts
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 0xc80409b7ef…1c072a
Audit this contract →
← previous block·next block →recent activity