← previous blocknext block →recent activity
Analyzing
Block #98,741,166
30 transactions · 19 stateful · 2026-08-24 11:04:06 UTC
Parallelism
93/100
Blocked
26%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,741,166 · 30 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
1w05w17w08w112w013w114w015w121w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba91cfa5…9f16
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xba91cfa5…9f0f
0x8964d7…10f8
4 touches
1 conflict
0xba91cfa5…9f10
0x8964d7…10f8
4 touches
1 conflict
0xba91cfa5…9f13
0x8964d7…10f8
4 touches
1 conflict
0xba91cfa5…9f14
0x8964d7…10f8
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xba91cfa50f…a79f16
Audit this contract →
← previous block·next block →recent activity