← previous blocknext block →recent activity
Analyzing
Block #98,604,996
18 transactions · 17 stateful · 2026-08-23 23:22:49 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,604,996 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w19w311w412w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc20bb30f…7331
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
6 touches
3 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
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 0xa6464996a2…6f3af9
Audit this contract →
← previous block·next block →recent activity