← previous blocknext block →recent activity
Analyzing
Block #98,661,181
33 transactions · 27 stateful · 2026-08-24 04:15:21 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,661,181 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w27w38w09w110w211w312w015w122w425w026w127w129w330w431w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x4e01a6b9…ed8e
0x34b655…2a6f
4 touches
1 conflict
0x7c1ccbd1…92bb
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity