← previous blocknext block →recent activity
Analyzing
Block #101,968,691
30 transactions · 26 stateful · 2026-09-04 18:13:07 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,968,691 · 30 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
1w03w14w26w18w213w014w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0x581b829b…9578
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x76e02d19…7609
0x34b655…2a6f
4 touches
1 conflict
0x7c216fca…20cb
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x91b13e914b…cb855d
Audit this contract →
← previous block·next block →recent activity