← previous blocknext block →recent activity
Analyzing
Block #101,661,860
16 transactions · 12 stateful · 2026-09-03 16:26:30 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,661,860 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17d87f0d…bfc5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x97705f96…75bf
0x34b655…2a6f
6 touches
3 conflicts
0x3e91bf83…a767
0x34b655…2a6f
6 touches
3 conflicts
0xe15e6ffd…014b
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa9ecfd66…5851
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 0x17d87f0d74…03bfc5
Audit this contract →
← previous block·next block →recent activity