← previous blocknext block →recent activity
Analyzing
Block #98,665,247
13 transactions · 13 stateful · 2026-08-24 04:36:32 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,665,247 · 13 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
2w04w15w27w18w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e5627d…6f8f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x5202eeec…466f
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x917ce24b…090d
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
6 conflicts on slot 0x68e5627d66…486f8f
Audit this contract →
← previous block·next block →recent activity