← previous blocknext block →recent activity
Analyzing
Block #101,924,026
19 transactions · 19 stateful · 2026-09-04 14:26:31 UTC
Parallelism
37/100
Blocked
68%
Avg conflicts / tx
2.21
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #101,924,026 · 19 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w310w715w816w917w1018w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
16 touches
28 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
14 touches
21 conflicts
0x21adef83…f2b7
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xa62eb46f…89b1
0x34b655…2a6f
8 touches
6 conflicts
0x8796ad81…d92f
0x34b655…2a6f
8 touches
6 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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
28 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity