← previous blocknext block →recent activity
Analyzing
Block #98,728,401
21 transactions · 21 stateful · 2026-08-24 09:59:53 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,728,401 · 21 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
3w04w15w27w08w19w310w411w112w013w114w215w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6415c9bf…6c16
0x34b655…2a6f
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x6227d2ea…73b4
0x40c49f…2af0
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6518075e…2b17
0x2a68ba…90c5
5 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
6 conflicts on slot 0x6415c9bf92…f66c16
Audit this contract →
← previous block·next block →recent activity