← previous blocknext block →recent activity
Analyzing
Block #106,035,778
16 transactions · 15 stateful · 2026-09-19 00:37:07 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,035,778 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a4b4833…cf01
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x48828733…fd48
0x34b655…2a6f
10 touches
10 conflicts
0x48b6f2c7…2ef7
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x1a4b483324…02cf01
Audit this contract →
← previous block·next block →recent activity