← previous blocknext block →recent activity
Analyzing
Block #98,502,441
19 transactions · 19 stateful · 2026-08-23 14:27:52 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,502,441 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w18w29w310w012w313w114w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
8 touches
6 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
8 touches
6 conflicts
0x29e8d1e2…e396
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0x1db5837f6b…d01264
Audit this contract →
← previous block·next block →recent activity