← previous blocknext block →recent activity
Analyzing
Block #100,119,729
35 transactions · 31 stateful · 2026-08-29 07:03:08 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,119,729 · 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
2w04w05w16w28w09w114w015w117w019w020w121w223w124w325w226w327w428w433w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddfee01…44bb
0x34b655…2a6f
10 touches
10 conflicts
0x00f25084…394d
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
6 touches
3 conflicts
0x627738d1…db02
0x34b655…2a6f
6 touches
3 conflicts
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
10 conflicts on slot 0x5ddfee0197…d044bb
Audit this contract →
← previous block·next block →recent activity