← previous blocknext block →recent activity
Analyzing
Block #98,504,705
13 transactions · 13 stateful · 2026-08-23 14:39:40 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,504,705 · 13 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
1w02w04w16w17w08w09w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb88ed4e…a342
0x34b655…2a6f
4 touches
1 conflict
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0x7ab71fc1…60f8
0xa6afd3…d132
4 touches
1 conflict
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
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
1 conflict on slot 0xeb88ed4e17…eaa342
Audit this contract →
← previous block·next block →recent activity