← previous blocknext block →recent activity
Analyzing
Block #101,672,142
15 transactions · 14 stateful · 2026-09-03 17:18:14 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,672,142 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w38w49w512w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x68596e3e…c6e6
0x34b655…2a6f
4 touches
1 conflict
0x6a925e11…2653
0x34b655…2a6f
4 touches
1 conflict
0x70f836c8…cf6d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity