← previous blocknext block →recent activity
Analyzing
Block #98,678,822
16 transactions · 15 stateful · 2026-08-24 05:47:17 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,678,822 · 16 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
1w02w03w15w16w29w310w411w514w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa61b7e3d…3786
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x63d7e3d6…5eb7
0x34b655…2a6f
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xa61b7e3d8e…c13786
Audit this contract →
← previous block·next block →recent activity