← previous blocknext block →recent activity
Analyzing
Block #106,464,327
40 transactions · 37 stateful · 2026-09-20 12:33:58 UTC
Parallelism
70/100
Blocked
62%
Avg conflicts / tx
1.7
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,464,327 · 40 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w07w28w110w011w012w113w214w317w320w423w124w526w227w129w630w731w832w933w1038w239w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54563e2b…7469
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
8 touches
6 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 0x54563e2be8…237469
Audit this contract →
← previous block·next block →recent activity