← previous blocknext block →recent activity
Analyzing
Block #101,974,732
16 transactions · 15 stateful · 2026-09-04 18:43:44 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
0.94
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,974,732 · 16 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
1w02w13w14w27w08w210w311w112w213w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x047ac470…ae63
0x34b655…2a6f
6 touches
3 conflicts
0x482d847a…5e74
0xd32edf…ff58
5 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xa8590d68…d5c8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity