← previous blocknext block →recent activity
Analyzing
Block #98,734,232
30 transactions · 27 stateful · 2026-08-24 10:29:13 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,734,232 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w29w011w113w214w317w018w119w220w321w422w123w024w126w127w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x905306ad…6fdd
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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: 0x40c49f17…d22af0
10 conflicts on slot 0x905306ad75…a36fdd
Audit this contract →
← previous block·next block →recent activity