← previous blocknext block →recent activity
Analyzing
Block #98,645,549
17 transactions · 17 stateful · 2026-08-24 02:53:43 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,645,549 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xef715e05…6a10
0x065c9d…c394
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xf2055a5a…92d3
0x34b655…2a6f
3 touches
1 conflict
0x48193d67…11a1
0x065c9d…c394
3 touches
1 conflict
0x9b9ba4a4…7429
0x065c9d…c394
3 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity