← previous blocknext block →recent activity
Analyzing
Block #101,936,966
13 transactions · 13 stateful · 2026-09-04 15:32:13 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,936,966 · 13 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
1w04w05w18w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x81b0da51…0d09
0x34b655…2a6f
4 touches
1 conflict
0xe3d3422c…0308
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity