← previous blocknext block →recent activity
Analyzing
Block #98,735,476
10 transactions · 10 stateful · 2026-08-24 10:35:28 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,735,476 · 10 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
1w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5684aadd…8d62
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xfd3f59bb…7b0e
0x34b655…2a6f
4 touches
1 conflict
0x122e2052…2bfe
0x34b655…2a6f
2 touches
0 conflicts
0x133a0592…5d51
0x34b655…2a6f
2 touches
0 conflicts
0x1e9a3fc4…c4e1
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x21b468a8…f015
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 0x5684aadd69…f58d62
Audit this contract →
← previous block·next block →recent activity