← previous blocknext block →recent activity
Analyzing
Block #101,985,727
14 transactions · 13 stateful · 2026-09-04 19:39:32 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,985,727 · 14 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
2w06w07w18w29w310w412w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247cfb80…cca8
0x34b655…2a6f
6 touches
3 conflicts
0x5845aae5…d85d
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x247cfb80ae…c4cca8
Audit this contract →
← previous block·next block →recent activity