← previous blocknext block →recent activity
Analyzing
Block #106,018,241
20 transactions · 19 stateful · 2026-09-18 23:08:52 UTC
Parallelism
40/100
Blocked
58%
Avg conflicts / tx
3.2
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,018,241 · 20 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
2w03w14w25w36w47w58w69w710w811w915w1019w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7011529e…456e
0x34b655…2a6f
22 touches
55 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
22 touches
55 conflicts
0x7c8cf338…6e72
0x34b655…2a6f
20 touches
45 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xcdcaadcf…1c9f
0x34b655…2a6f
20 touches
45 conflicts
0x4c572488…35d9
0x34b655…2a6f
18 touches
36 conflicts
0x4cff6b80…47a8
0x34b655…2a6f
18 touches
36 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
55 conflicts on slot 0x7011529e7e…ad456e
Audit this contract →
← previous block·next block →recent activity