← previous blocknext block →recent activity
Analyzing
Block #98,754,108
33 transactions · 28 stateful · 2026-08-24 12:09:17 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,754,108 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w37w08w19w210w313w114w420w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc138afd8…2769
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd25997d0…a684
0x1b6862…e19c
8 touches
6 conflicts
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 0xc138afd802…f02769
Audit this contract →
← previous block·next block →recent activity