← previous blocknext block →recent activity
Analyzing
Block #106,216,673
27 transactions · 26 stateful · 2026-09-19 15:47:33 UTC
Parallelism
78/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,673 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w114w217w218w319w420w521w022w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05387b2…9c83
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0xe3f2be0f…f51f
0x34b655…2a6f
6 touches
3 conflicts
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
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
15 conflicts on slot 0xa05387b2b9…1a9c83
Audit this contract →
← previous block·next block →recent activity