← previous blocknext block →recent activity
Analyzing
Block #100,630,194
20 transactions · 17 stateful · 2026-08-31 01:55:35 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,630,194 · 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
1w02w13w24w06w17w29w317w418w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a3fecf6…b414
0xc8689a…ee79
8 touches
6 conflicts
0x1dedc384…ff57
0x851145…3f07
8 touches
6 conflicts
0x2ce5d13f…f8a9
0x851145…3f07
8 touches
6 conflicts
0x474e5df9…821f
0x851145…3f07
8 touches
6 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
8 touches
6 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
8 touches
6 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: Settlement / Helper
6 conflicts on slot 0x8a3fecf6d7…5cb414
Audit this contract →
← previous block·next block →recent activity