← previous blocknext block →recent activity
Analyzing
Block #106,385,413
28 transactions · 25 stateful · 2026-09-20 05:56:46 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,385,413 · 28 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
13w014w115w216w318w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x36d7075f…d5c9
0x34b655…2a6f
12 touches
15 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0x3080fd80…120a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xaa71850b…95ea
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
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
21 conflicts on slot 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity