← previous blocknext block →recent activity
Analyzing
Block #98,504,211
19 transactions · 18 stateful · 2026-08-23 14:37:06 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,504,211 · 19 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
1w04w05w16w09w110w011w112w213w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556907da…32e7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8c52ced7…6625
0x34b655…2a6f
6 touches
3 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
4 touches
1 conflict
0x77b7b407…ea83
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9068a9bc…86ee
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x556907daa8…0232e7
Audit this contract →
← previous block·next block →recent activity