← previous blocknext block →recent activity
Analyzing
Block #98,740,983
30 transactions · 26 stateful · 2026-08-24 11:03:10 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,740,983 · 30 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
1w02w13w26w09w311w117w018w119w220w321w422w123w224w327w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3401c0d8…0a36
0x40c49f…2af0
10 touches
10 conflicts
0x3a921be0…779c
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x872e51c8…ae26
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: 0x40c49f17…d22af0
10 conflicts on slot 0x3401c0d8ec…d70a36
Audit this contract →
← previous block·next block →recent activity