← previous blocknext block →recent activity
Analyzing
Block #105,684,204
17 transactions · 17 stateful · 2026-09-17 19:05:13 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,684,204 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w110w011w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0xe561281f…7569
0x34b655…2a6f
6 touches
3 conflicts
0x1b7bc769…9e4a
0x34b655…2a6f
6 touches
3 conflicts
0xfa24929f…7992
0x34b655…2a6f
6 touches
3 conflicts
0x62406c85…e348
0x34b655…2a6f
6 touches
3 conflicts
0x07d94be1…7fa8
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity