← previous blocknext block →recent activity
Analyzing
Block #106,015,495
23 transactions · 21 stateful · 2026-09-18 22:55:03 UTC
Parallelism
52/100
Blocked
71%
Avg conflicts / tx
2.48
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,015,495 · 23 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
1w03w14w25w36w47w58w69w712w714w115w118w820w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
18 touches
36 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x48828733…fd48
0x34b655…2a6f
16 touches
28 conflicts
0x69d2053b…935a
0x34b655…2a6f
16 touches
28 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
14 touches
21 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
14 touches
21 conflicts
0xa57a72ed…64c2
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity