← previous blocknext block →recent activity
Analyzing
Block #98,473,932
32 transactions · 22 stateful · 2026-08-23 12:03:45 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,473,932 · 32 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
1w02w03w06w17w18w110w011w112w213w014w115w227w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78efe143…580b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x20082abc…c18d
0xd32edf…ff58
7 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x4c7c2471…43d7
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 0x78efe14337…61580b
Audit this contract →
← previous block·next block →recent activity