← previous blocknext block →recent activity
Analyzing
Block #98,749,221
20 transactions · 19 stateful · 2026-08-24 11:44:37 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,749,221 · 20 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
1w03w04w15w010w112w213w314w416w017w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0xa7c806f6…f2ea
0x34b655…2a6f
6 touches
3 conflicts
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0x9fcd60ee…673c
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: Perpl
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity