← previous blocknext block →recent activity
Analyzing
Block #98,755,047
19 transactions · 17 stateful · 2026-08-24 12:14:01 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,755,047 · 19 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
1w02w13w06w08w210w111w112w013w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f0b45b3…e2fb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc8c9c001…2a5a
0xd32edf…ff58
5 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
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 0x4f0b45b368…41e2fb
Audit this contract →
← previous block·next block →recent activity