← previous blocknext block →recent activity
Analyzing
Block #101,022,419
30 transactions · 27 stateful · 2026-09-01 10:49:04 UTC
Parallelism
73/100
Blocked
63%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,022,419 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w310w012w113w215w317w418w520w622w724w125w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
10 touches
10 conflicts
0xe569ddfe…86f9
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x336486a4…20bd
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
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
10 conflicts on slot 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity