← previous blocknext block →recent activity
Analyzing
Block #98,428,510
31 transactions · 25 stateful · 2026-08-23 08:14:53 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,428,510 · 31 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
1w02w04w17w29w010w111w012w118w019w120w221w322w123w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x2a68f906…d441
0xd32edf…ff58
5 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x092c3ada…6307
0x34b655…2a6f
4 touches
1 conflict
0x1e6851c8…a244
0x34b655…2a6f
4 touches
1 conflict
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x588ba065…f516
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity