← previous blocknext block →recent activity
Analyzing
Block #99,779,419
35 transactions · 25 stateful · 2026-08-28 02:27:04 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,779,419 · 35 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
13w014w018w119w223w027w328w129w230w432w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d017b93…8081
0x34b655…2a6f
8 touches
6 conflicts
0xd58d4996…ef66
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9468938d…a2ea
0xd32edf…ff58
5 touches
3 conflicts
0x119b7e47…d29c
0x34b655…2a6f
4 touches
1 conflict
0xaa1cc6ac…4e23
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x9d017b9313…e88081
Audit this contract →
← previous block·next block →recent activity