← previous blocknext block →recent activity
Analyzing
Block #101,893,026
23 transactions · 16 stateful · 2026-09-04 11:49:22 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,893,026 · 23 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
2w03w14w25w06w17w213w320w021w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x33761f7c…8f85
0x34b655…2a6f
8 touches
6 conflicts
0x6df1d50f…8a92
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d19cd25…a3c2
0x34b655…2a6f
6 touches
3 conflicts
0xe3a4bca8…9120
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0xa90eb29b…2cec
0x34b655…2a6f
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity