← previous blocknext block →recent activity
Analyzing
Block #98,736,203
19 transactions · 17 stateful · 2026-08-24 10:39:07 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,736,203 · 19 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
2w03w14w15w09w110w214w317w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x30f6037e…f6be
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3b
0x34b655…2a6f
4 touches
1 conflict
0xaad41694…315e
0x34b655…2a6f
4 touches
1 conflict
0xaca60768…7272
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity