← previous blocknext block →recent activity
Analyzing
Block #99,183,385
46 transactions · 33 stateful · 2026-08-26 00:15:58 UTC
Parallelism
83/100
Blocked
64%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,183,385 · 46 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w010w111w212w313w314w125w426w527w628w232w333w534w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity