← previous blocknext block →recent activity
Analyzing
Block #98,100,413
33 transactions · 26 stateful · 2026-08-22 04:43:29 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,100,413 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w18w211w112w015w316w217w318w120w222w426w428w531w632w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x04a53fbd…0ac5
0x34b655…2a6f
6 touches
3 conflicts
0x0f21939a…e878
0x34b655…2a6f
6 touches
3 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity