← previous blocknext block →recent activity
Analyzing
Block #101,955,111
16 transactions · 15 stateful · 2026-09-04 17:04:19 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,955,111 · 16 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
1w02w13w24w05w17w18w29w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc6d8507c…0e1d
0x34b655…2a6f
4 touches
1 conflict
0xc852b267…9d14
0x34b655…2a6f
4 touches
1 conflict
0xcda08bf3…082e
0x34b655…2a6f
4 touches
1 conflict
0xdac8e13c…bc65
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
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