← previous blocknext block →recent activity
Analyzing
Block #108,997,436
33 transactions · 25 stateful · 2026-09-29 09:12:33 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.24
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #108,997,436 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w114w216w317w418w519w621w724w830w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x5897dd6b…7629
0x34b655…2a6f
10 touches
10 conflicts
0x3a00de10…175c
0x34b655…2a6f
8 touches
6 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0057
0x1b6862…e19c
4 touches
1 conflict
0x16445c4f…3d33
0x1b6862…e19c
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity