← previous blocknext block →recent activity
Analyzing
Block #106,376,524
28 transactions · 27 stateful · 2026-09-20 05:12:02 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,376,524 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w07w08w09w112w114w119w423w524w627w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2facdba…7a7e
0x34b655…2a6f
12 touches
15 conflicts
0xd8916bd7…6415
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x381b67a9…7272
0x34b655…2a6f
10 touches
10 conflicts
0x17bb579f…938c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
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 0xd2facdbaf5…4f7a7e
Audit this contract →
← previous block·next block →recent activity