← previous blocknext block →recent activity
Analyzing
Block #101,665,428
17 transactions · 16 stateful · 2026-09-03 16:44:27 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,665,428 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w112w013w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8f4e041c…01ae
0x34b655…2a6f
4 touches
1 conflict
0xa2c04336…e4c0
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xb826ef15…d248
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
1 conflict on slot 0x173b64af39…0f6c43
Audit this contract →
← previous block·next block →recent activity