← previous blocknext block →recent activity
Analyzing
Block #103,212,888
39 transactions · 35 stateful · 2026-09-09 03:03:03 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #103,212,888 · 39 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
1w02w13w04w05w26w37w38w09w110w215w416w017w121w022w123w224w025w127w028w130w231w333w536w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x20c6f08f…36e5
0x34b655…2a6f
6 touches
3 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity