← previous blocknext block →recent activity
Analyzing
Block #101,658,696
25 transactions · 22 stateful · 2026-09-03 16:10:35 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,658,696 · 25 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
1w02w13w26w07w18w09w110w211w312w316w117w221w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf459817b…c916
0x34b655…2a6f
8 touches
6 conflicts
0x024b482b…16b0
0x34b655…2a6f
8 touches
6 conflicts
0x1a2e73cf…5ff5
0x34b655…2a6f
8 touches
6 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xb40e601f…bf98
0x34b655…2a6f
8 touches
6 conflicts
0xb826ef15…d248
0x34b655…2a6f
8 touches
6 conflicts
0xba149d38…48fe
0x34b655…2a6f
8 touches
6 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 0xf459817b5d…00c916
Audit this contract →
← previous block·next block →recent activity