← previous blocknext block →recent activity
Analyzing
Block #98,670,906
17 transactions · 17 stateful · 2026-08-24 05:06:01 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,670,906 · 17 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
2w03w14w05w16w08w29w210w013w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98db8ee…a56d
0x34b655…2a6f
4 touches
1 conflict
0x8f84702c…c5f9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
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
1 conflict on slot 0xf98db8ee72…13a56d
Audit this contract →
← previous block·next block →recent activity