← previous blocknext block →recent activity
Analyzing
Block #98,507,838
24 transactions · 23 stateful · 2026-08-23 14:55:52 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,507,838 · 24 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
1w02w13w15w07w18w19w010w211w114w115w316w118w219w320w221w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0x8821957d…7040
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x39c589a4…3de4
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
6 conflicts on slot 0xbb1747e217…82f78b
Audit this contract →
← previous block·next block →recent activity