← previous blocknext block →recent activity
Analyzing
Block #106,389,482
28 transactions · 27 stateful · 2026-09-20 06:17:15 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,389,482 · 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
2w03w19w210w311w413w314w515w616w726w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e2dba2f…1a55
0x34b655…2a6f
12 touches
15 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x39f86166…2fa2
0x34b655…2a6f
8 touches
6 conflicts
0xa2a43c00…b9a7
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 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 0x3e2dba2f86…501a55
Audit this contract →
← previous block·next block →recent activity