← previous blocknext block →recent activity
Analyzing
Block #98,580,927
24 transactions · 22 stateful · 2026-08-23 21:17:17 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,580,927 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w111w212w313w014w418w121w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b10f1de…fc43
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57e524ee…c642
0x34b655…2a6f
4 touches
1 conflict
0x68237c6e…42e1
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 0x0b10f1de2a…acfc43
Audit this contract →
← previous block·next block →recent activity