← previous blocknext block →recent activity
Analyzing
Block #106,015,492
29 transactions · 25 stateful · 2026-09-18 22:55:02 UTC
Parallelism
35/100
Blocked
80%
Avg conflicts / tx
5.62
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,015,492 · 29 txs across 19 waves · depth 19
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1013w1122w1324w1425w1526w1627w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
32 touches
120 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
28 touches
91 conflicts
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0x48828733…fd48
0x34b655…2a6f
22 touches
55 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
22 touches
55 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
22 touches
55 conflicts
0x7c8cf338…6e72
0x34b655…2a6f
22 touches
55 conflicts
0x97394169…cfc0
0x34b655…2a6f
22 touches
55 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
120 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity