← previous blocknext block →recent activity
Analyzing
Block #101,061,656
29 transactions · 22 stateful · 2026-09-01 14:06:28 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,061,656 · 29 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
1w08w09w011w012w114w015w016w118w120w221w225w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x2edda1ab…e380
0x8964d7…10f8
6 touches
3 conflicts
0x2edda1ab…e381
0x8964d7…10f8
6 touches
3 conflicts
0x2edda1ab…e384
0x8964d7…10f8
6 touches
3 conflicts
0x2edda1ab…e385
0x8964d7…10f8
6 touches
3 conflicts
0x2edda1ab…e387
0x8964d7…10f8
6 touches
3 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity